GPFS client

By -
GPFS Client add steps

SUSE
Install rpm on client machine  Kernel and kernel-default-devel should be installed in server and versions should be same.
psmb:~ # rpm -qa |grep kernel
nfs-kernel-server-1.2.3-18.33.1
kernel-firmware-20110923-0.52.3
linux-kernel-headers-2.6.32-1.15.1
kernel-default-base-3.0.101-0.31.1
kernel-default-base-3.0.101-0.35.1
kernel-default-3.0.101-0.31.1
psmb:~ # zypper
psmb:~ # vi /etc/zypp/repos.d/
SUSE-Linux-Enterprise-Server-11-SP3 11.3.3-1.138.repo  sle-11-x86_64.repo
rrr/
psmb:~ # vi /etc/zypp/repos.d/sle-11-x86_64.repo


tar -zxvf gpfs353_x86_64.tar.gz

rpm -ivh gpfs353_x86_64/*

export PATH=$PATH:/usr/lpp/mmfs/bin/

vi /etc/bash.bashrc  --> add above command in this files

cd /usr/lpp/mmfs/src/

Command 1
make Autoconfig   --> some times it gives error mostly due to kernel and kernel-devel version mismatch . read readme file "/usr/lpp/mmfs/src/README"

"cpp present
gcc present
g++ present
ld present"

Command 2
make World

Command 3
make InstallImages

ssh-copy-id -i root@gpfs1

ssh-copy-id -i root@gpfs2

SERVER side commands : GPFS1

vi /etc/hosts  --> add client entry if it is not available in DNS

mmaddnode -N psmb:nonquorum-client

mmlslicense

mmchlicense client --accept -N psmb

mmlslicense

mmgetstate -a

mmstartup -N psmb

more details : tail -f /var/adm/ras/mmfs.log.latest

mmlsnsd -m

mmdf mc_installers

 mmdf mc_installers --block-size auto












 Run

 [root@GPFS1 GPFS]# ls -l /dev/mapper/
total 0
crw-rw---- 1 root root 10, 58 Dec  2 12:09 control
lrwxrwxrwx 1 root root      7 Dec  3 12:20 mpath0 -> ../dm-3
lrwxrwxrwx 1 root root      7 Dec  3 09:47 mpath0p1 -> ../dm-7
lrwxrwxrwx 1 root root      7 Dec  3 12:20 mpath1 -> ../dm-4
lrwxrwxrwx 1 root root      7 Dec  3 09:47 mpath1p1 -> ../dm-9
lrwxrwxrwx 1 root root      7 Dec  3 12:20 mpath2 -> ../dm-5
lrwxrwxrwx 1 root root      8 Dec  3 09:47 mpath2p1 -> ../dm-10
lrwxrwxrwx 1 root root      7 Dec  3 12:20 mpath3 -> ../dm-6
lrwxrwxrwx 1 root root      8 Dec  3 09:47 mpath3p1 -> ../dm-11
lrwxrwxrwx 1 root root      8 Dec  3 12:20 mpath4 -> ../dm-13
lrwxrwxrwx 1 root root      8 Dec  3 09:47 mpath4p1 -> ../dm-14
lrwxrwxrwx 1 root root      7 Dec  3 12:20 mpath5 -> ../dm-8
lrwxrwxrwx 1 root root      8 Dec  3 09:47 mpath5p1 -> ../dm-12
lrwxrwxrwx 1 root root      8 Dec  3 12:20 mpath6 -> ../dm-15
lrwxrwxrwx 1 root root      8 Dec  3 12:20 mpath6p1 -> ../dm-16
lrwxrwxrwx 1 root root      7 Dec  2 12:13 VolGroup-lv_home -> ../dm-2
lrwxrwxrwx 1 root root      7 Dec  2 12:09 VolGroup-lv_root -> ../dm-0
lrwxrwxrwx 1 root root      7 Dec  2 12:09 VolGroup-lv_swap -> ../dm-1

[root@GPFS1 GPFS]# cat HOME_disks.lst
%nsd:
device=/dev/dm-3
servers=gpfs1,gpfs2
usage=dataAndMetadata

%nsd:
device=/dev/dm-6
servers=gpfs1,gpfs2
usage=dataAndMetadata

%nsd:
device=/dev/dm-8
servers=gpfs1,gpfs2
usage=dataAndMetadata

%nsd:
device=/dev/dm-15
servers=gpfs1,gpfs2
usage=dataAndMetadata

[root@GPFS1 GPFS]# mmcrnsd -F HOME_disks.lst -v no
mmcrnsd: Processing disk dm-3
mmcrnsd: Processing disk dm-6
mmcrnsd: Processing disk dm-8
mmcrnsd: Processing disk dm-15
mmcrnsd: Propagating the cluster configuration data to all
  affected nodes.  This is an asynchronous process.
[root@GPFS1 GPFS]# mmlsnsd

 File system   Disk name    NSD servers
---------------------------------------------------------------------------
 mc_installers gpfs1nsd     GPFS1.blr.stglabs.ibm.com,GPFS2.blr.stglabs.ibm.com
 mc_installers gpfs2nsd     GPFS1.blr.stglabs.ibm.com,GPFS2.blr.stglabs.ibm.com
 (free disk)   gpfs3nsd     GPFS1.blr.stglabs.ibm.com,GPFS2.blr.stglabs.ibm.com
 (free disk)   gpfs4nsd     GPFS1.blr.stglabs.ibm.com,GPFS2.blr.stglabs.ibm.com
 (free disk)   gpfs5nsd     GPFS1.blr.stglabs.ibm.com,GPFS2.blr.stglabs.ibm.com
 (free disk)   gpfs6nsd     GPFS1.blr.stglabs.ibm.com,GPFS2.blr.stglabs.ibm.com

[root@GPFS1 GPFS]# mmlsnsd -m

 Disk name    NSD volume ID      Device         Node name                Remarks
---------------------------------------------------------------------------------------
 gpfs1nsd     097E8A43547EB4EE   /dev/dm-4      GPFS1.blr.stglabs.ibm.com server node
 gpfs1nsd     097E8A43547EB4EE   /dev/dm-4      GPFS2.blr.stglabs.ibm.com server node
 gpfs2nsd     097E8A43547EB4F1   /dev/dm-5      GPFS1.blr.stglabs.ibm.com server node
 gpfs2nsd     097E8A43547EB4F1   /dev/dm-2      GPFS2.blr.stglabs.ibm.com server node
 gpfs3nsd     097E8A4354814121   /dev/dm-3      GPFS1.blr.stglabs.ibm.com server node
 gpfs3nsd     097E8A4354814121   /dev/dm-9      GPFS2.blr.stglabs.ibm.com server node
 gpfs4nsd     097E8A4354814123   /dev/dm-6      GPFS1.blr.stglabs.ibm.com server node
 gpfs4nsd     097E8A4354814123   /dev/dm-3      GPFS2.blr.stglabs.ibm.com server node
 gpfs5nsd     097E8A4354814126   /dev/dm-8      GPFS1.blr.stglabs.ibm.com server node
 gpfs5nsd     097E8A4354814126   /dev/dm-6      GPFS2.blr.stglabs.ibm.com server node
 gpfs6nsd     097E8A4354814128   /dev/dm-15     GPFS1.blr.stglabs.ibm.com server node
 gpfs6nsd     097E8A4354814128   /dev/dm-8      GPFS2.blr.stglabs.ibm.com server node


 [root@GPFS1 GPFS]# mmcrfs mc_home -F HOME_disks.lst -B 64k -T /home -A yes

The following disks of mc_home will be formatted on node GPFS2.blr.stglabs.ibm.com:
    gpfs3nsd: size 1073741824 KB
    gpfs4nsd: size 2147483648 KB
    gpfs5nsd: size 2147483648 KB
    gpfs6nsd: size 4194304 KB
Formatting file system ...
Disks up to size 18 TB can be added to storage pool system.
Creating Inode File
Creating Allocation Maps
Creating Log Files
Clearing Inode Allocation Map
Clearing Block Allocation Map
Formatting Allocation Map for storage pool system
Completed creation of file system /dev/mc_home.
mmcrfs: Propagating the cluster configuration data to all
  affected nodes.  This is an asynchronous process.

 

 mmcrnsd -F INSTALLERS_disks.lst -v no
  943  vi INSTALLERS_disks.lst
  944  mmlsnsd
  945  mmlsnsd -m
  946  man mmcrfs
  947  mmcrfs mc_installers -F INSTALLERS_disks.lst -B 64k -T /mc_installers -A yes
  948  mmmount all -a
  949  df -TH
  950  mmlsfs mc_installers
  951  mmdf mc_installers



log files:
tail -f /var/adm/ras/mmfs.log.latest

Error :
unable to active PSMB
psmb:/usr/lpp/mmfs/src # tail -f /var/adm/ras/mmfs.log.latest
Thu Dec  4 13:18:37 IST 2014: runmmfs starting
Removing old /var/adm/ras/mmfs.log.* files:
Unloading modules from /lib/modules/3.0.101-0.31-default/extra
runmmfs: The /lib/modules/3.0.101-0.31-default/extra/mmfslinux.ko kernel extension does not exist.
runmmfs: Unable to verify kernel/module configuration.
Loading modules from /lib/modules/3.0.101-0.31-default/extra
runmmfs: The /lib/modules/3.0.101-0.31-default/extra/mmfslinux.ko kernel extension does not exist.
runmmfs: Unable to verify kernel/module configuration.
Thu Dec  4 13:18:37 IST 2014 runmmfs: error in loading or unloading the mmfs kernel extension
Thu Dec  4 13:18:37 IST 2014 runmmfs: stopping GPFS

Comments

Post a Comment

Popular posts from this blog

How to delete SEA in VIOS

By -
Remove the network en0 #ifconfig en0 down #ifconfig en0 detach Delete SEA $ lsdev -type sea name             status      description ent27            Defined     Shared Ethernet Adapter $ chdev -dev en26 -attr state=detach en27 changed $ rmdev -dev ent26;rmdev -dev en26;rmdev -dev et26 ent27 deleted $ rmdev -dev en26 en27 deleted $ rmdev -dev et26 et27 deleted system information #prtconf|more rmdev -dev ent3;rmdev -dev en3;rmdev -dev et3
Read more

Webmin configuration for LDAP

By -
We cannot add or delete users by default so we have to do below changes in LDAP module in GUI mode only. Configuring the module The most complex part of using this module is configuring it to talk to your LDAP server. By default, it will attempt to auto-detect the settings by looking at the LDAP client settings on your system, documented on the LDAPClient page. However, if this fails (perhaps because the LDAP server is not one of its own clients), you will need to configure the module manually as follows : On the module's main page, click on the Module Config link. In the LDAP server host field, enter the hostname of your LDAP server. If it is running on the same machine, enter localhost. If the LDAP server is using encryption, change the LDAP server uses TLS? option to Yes. In the Bind to LDAP server as field, enter the full DN of the administrative user for your LDAP server. This might be something like cn=Manager,dc=my-domain,dc=com. In the Credentials for bind name above field,...
Read more

Sample questions and answers for AWS Associate Solutions Architect Certification ---> AWS exam dumps

By -
Sample questions and answers for AWS Associate Solutions Architect Certification I try to give value for this by providing more information than the answer Q.What does Amazon S3 stand for? A.Simple Storage Service. Q:You must assign each server to at least _____ security group A:1  Q:Before I delete an EBS volume, what can I do if I want to recreate the volume later? A:Store a snapshot of the volume  http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-deleting-volume.html Q:Select the most correct answer: The device name /dev/sda1 (within Amazon EC2 ) is _____ A:Reserved for the root device  Q:If I want an instance to have a public IP address, which IP address should I use? A:Elastic IP Address http://aws.amazon.com/articles/1346 Q:What does RRS stand for when talking about S3? A:Reduced Redundancy Storage  http://aws.typepad.com/aws/2010/05/new-amazon-s3-reduced-redundancy-storage-rrs.html Q:All Amazon EC2 instances are assigned two IP addresses at lau...
Read more