HP StorageWorks Scalable File Share - Manual (Page 65)

7.9 Misconfigured Lustre target config logs due to incorrect CSV file used
during lustre_config
This problem has been identified with HP SFS G3.0 and systems that have been upgraded to HP
SFS G3.1 or HP SFS G3.2 from HP SFS G3.0 without file system re-creation. The CSV file
/opt/hp/sfs/scripts/testfs.csv
shown below as supplied with HP SFS G3.0 is incorrect.
[root]# cat /opt/hp/sfs/scripts/testfs.csv
#hostname, module_opts, device name, mount point, device type, fsname, mgs nids, index,format options, mkfs
options, mount options, failover nids
n1,options lnet networks=o2ib0,/dev/mapper/mpath4,/mnt/mgs,mgs,testfs,,,,,"_netdev,noauto",icn2@o2ib0
n2,options lnet networks=o2ib0,/dev/mapper/mpath5,/mnt/mds,mdt,testfs,icn1@o2ib0,,,,"_netdev,noauto",icn1@o2ib0
n3,options lnet networks=o2ib0,/dev/mapper/mpath8,/mnt/ost0,ost,testfs,icn1@o2ib0,0,,,"_netdev,noauto",icn4@o2ib0
n3,options lnet networks=o2ib0,/dev/mapper/mpath9,/mnt/ost1,ost,testfs,icn1@o2ib0,1,,,"_netdev,noauto",icn4@o2ib0
n3,options lnet networks=o2ib0,/dev/mapper/mpath10,/mnt/ost2,ost,testfs,icn1@o2ib0,2,,,"_netdev,noauto",icn4@o2ib0
n3,options lnet networks=o2ib0,/dev/mapper/mpath11,/mnt/ost3,ost,testfs,icn1@o2ib0,3,,,"_netdev,noauto",icn4@o2ib0
n4,options lnet networks=o2ib0,/dev/mapper/mpath12,/mnt/ost4,ost,testfs,icn1@o2ib0,4,,,"_netdev,noauto",icn3@o2ib0
n4,options lnet networks=o2ib0,/dev/mapper/mpath13,/mnt/ost5,ost,testfs,icn1@o2ib0,5,,,"_netdev,noauto",icn3@o2ib0
n4,options lnet networks=o2ib0,/dev/mapper/mpath14,/mnt/ost6,ost,testfs,icn1@o2ib0,6,,,"_netdev,noauto",icn3@o2ib0
n4,options lnet networks=o2ib0,/dev/mapper/mpath15,/mnt/ost7,ost,testfs,icn1@o2ib0,7,,,"_netdev,noauto",icn3@o2ib0
… … … … … … … … …
… … … … … … … … …
[root]#
The correct CSV file /opt/hp/sfs/scripts/testfs.csv should contain two colon separated
MGS nids, as shown below.
[root]# cat /opt/hp/sfs/scripts/testfs.csv
#hostname, module_opts, device name, mount point, device type, fsname, mgs nids, index,format options, mkfs
options, mount options, failover nids
n1,options lnet networks=o2ib0,/dev/mapper/mpath4,/mnt/mgs,mgs,testfs,,,,,"_netdev,noauto",icn2@o2ib0
n2,options lnet
networks=o2ib0,/dev/mapper/mpath5,/mnt/mds,mdt,testfs,icn1@o2ib0:icn2@o2ib0,,,,"_netdev,noauto",icn1@o2ib0
n3,options lnet
networks=o2ib0,/dev/mapper/mpath8,/mnt/ost0,ost,testfs,icn1@o2ib0:icn2@o2ib0,0,,,"_netdev,noauto",icn4@o2ib0
n3,options lnet
networks=o2ib0,/dev/mapper/mpath9,/mnt/ost1,ost,testfs,icn1@o2ib0:icn2@o2ib0,1,,,"_netdev,noauto",icn4@o2ib0
n3,options lnet
networks=o2ib0,/dev/mapper/mpath10,/mnt/ost2,ost,testfs,icn1@o2ib0:icn2@o2ib0,2,,,"_netdev,noauto",icn4@o2ib0
n3,options lnet
networks=o2ib0,/dev/mapper/mpath11,/mnt/ost3,ost,testfs,icn1@o2ib0:icn2@o2ib0,3,,,"_netdev,noauto",icn4@o2ib0
n4,options lnet
networks=o2ib0,/dev/mapper/mpath12,/mnt/ost4,ost,testfs,icn1@o2ib0:icn2@o2ib0,4,,,"_netdev,noauto",icn3@o2ib0
n4,options lnet
networks=o2ib0,/dev/mapper/mpath13,/mnt/ost5,ost,testfs,icn1@o2ib0:icn2@o2ib0,5,,,"_netdev,noauto",icn3@o2ib0
n4,options lnet
networks=o2ib0,/dev/mapper/mpath14,/mnt/ost6,ost,testfs,icn1@o2ib0:icn2@o2ib0,6,,,"_netdev,noauto",icn3@o2ib0
n4,options lnet
networks=o2ib0,/dev/mapper/mpath15,/mnt/ost7,ost,testfs,icn1@o2ib0:icn2@o2ib0,7,,,"_netdev,noauto",icn3@o2ib0
… … … … … … … … …
… … … … … … … … …
[root]#
Using the incorrect CSV file during the initial lustre_config HP SFS file system creation step
results in incorrect configuration log information on HP SFS targets (MDT and OSTs). Verify
your configuration with the tunefs.lustre --print /dev/mapper/mpathX command.
If the output on MDT and OST target mpath devices shows two mgsnode parameter entries,
your configuration is correct. For example:
Incorrect configuration output
Parameters: mgsnode=172.31.100.1@o2ib failover.node=172.31.100.1@o2ib
Correct configuration output
Parameters: mgsnode=172.31.100.1@o2ib mgsnode=172.31.100.2@o2ib
failover.node=172.31.100.2@o2ib
This configuration log information affects Lustre functionality. Lustre may not work as expected
in the event of certain HP SFS server node failure scenarios.
If your HP SFS G3.x system is configured with the incorrect CSV file format, carefully examine
the CSV file tunefs.lustre --print /dev/mapper/mpathX output on all HP SFS targets
7.9 Misconfigured Lustre target config logs due to incorrect CSV file used during lustre_config 65