Importing a file system and a recovery group on a new ECE cluster
Use the mmimportfs command to import desired file system(s) into the new cluster.
Prepare a cluster that imports a file system and a recovery group:
- Migrate the drives from the old server to the new server on the destination cluster. Consult the hardware vendor for the safety migration procedure.
- Prepare the drives mapping configuration file on the destination servers. For more information, see Setting up IBM Storage Scale Erasure Code Edition for disk slot location.
- Issue the following command to create a new node class and node assignments to match the
configuration of an original
cluster:
# mmvdisk nodeclass create --node-class ClassName -N Node[,Node...]
- Issue the following command to configure servers of the node class before you import a file
system and a recovery
group:
# mmvdisk server configure --node-class NodeClass --recycle one
For more information about the mmimportfs command, see the mmexportfs command in the IBM Storage Scale: Command and Programming Reference Guide in the IBM Storage Scale documentation.
-
Import a file system into a new cluster by using the mmimportfs
command.
A sample output is as follows:# mmimportfs test_fs1 -i export
mmimportfs: Processing file system test_fs1 ... mmimportfs: Processing disk RG001LG001VS001 mmimportfs: Processing disk RG001LG002VS001 mmimportfs: Processing disk RG001LG003VS001 mmimportfs: Processing disk RG001LG004VS001 mmimportfs: Processing disk RG001LG005VS001 mmimportfs: Processing disk RG001LG006VS001 mmimportfs: Processing disk RG001LG007VS001 mmimportfs: Processing disk RG001LG008VS001 mmimportfs: Validating pdisk consistency for Scale-out nodes mmimportfs: Committing the changes ... mmimportfs: The following file systems were successfully imported: test_fs1 mmimportfs: Propagating the cluster configuration data to all affected nodes. mmimportfs: Activated recovery group rg1. mmimportfs: Drives are inserted correctly on all nodes for RG rg1 mmimportfs: Updating RG Status ... mmimportfs: Propagating the cluster configuration data to all affected nodes.
For example,- If the new cluster has nodes or node classes with different names from in the original, create a
stanza file to specify the new names.
%rg: rgName=rg1 servers=c72f3u54-eth0,c72f3u22-eth0,c72f3u11-eth0,c72f3u15-eth0 nodeclass=nc2
- Use the -S option with the mmimportfs command to make use
of the stanza file.
# mmimportfs test_fs1 -i export -S stanzaFile
- If the new cluster has nodes or node classes with different names from in the original, create a
stanza file to specify the new names.
- Check state of the imported file systems and recovery groups.
- Check the file systems status.
A sample output is as follows:# mmvdisk fs list --fs test_fs1
vdisk with list of holds holds storage vdisk set recovery group count trim failure groups metadata data pool -------------- -------------- ----- ---- -------------- -------- ----- ------- VS1 rg1 8 0 1, 2 yes yes system
- Check the recovery groups
status.
A sample output is as follows:mmvdisk rg list --rg rg1 --da --server --vdisk-set --pdisk
node number server active remarks ------ -------------------------------- ------- ------- 3 c72f3u25-eth0 yes serving rg1: LG002, LG006 1 c72f3u27-eth0 yes serving rg1: root, LG004, LG008 2 c72f3u29-eth0 yes serving rg1: LG001, LG005 4 c72f3u31-eth0 yes serving rg1: LG003, LG007 declustered needs vdisks pdisks capacity array service type BER trim user log total spare rt total raw free raw background task ----------- ------- ---- ------- ---- ---- --- ----- ----- -- --------- -------- --------------- DA1 no HDD enable no 8 9 16 2 2 24 TiB 12 TiB scrub 14d (61%) mmvdisk: Total capacity is the raw space before any vdisk set definitions. mmvdisk: Free capacity is what remains for additional vdisk set definitions. declustered paths AU pdisk array active total capacity free space log size state ------------ ----------- ------ ----- -------- ---------- -------- ----- n001p001 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n001p002 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n001p003 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n001p004 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n002p001 DA1 1 1 1863 GiB 1024 GiB 3072 MiB ok n002p002 DA1 1 1 1863 GiB 1016 GiB 3072 MiB ok n002p003 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n002p004 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n003p001 DA1 1 1 1863 GiB 1018 GiB 3072 MiB ok n003p002 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n003p003 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n003p004 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n004p001 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n004p002 DA1 1 1 1863 GiB 1018 GiB 3072 MiB ok n004p003 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok n004p004 DA1 1 1 1863 GiB 1017 GiB 3072 MiB ok declustered capacity all vdisk sets defined recovery group array type total raw free raw free% in the declustered array -------------- ----------- ---- --------- -------- ----- ------------------------ rg1 DA1 HDD 24 TiB 12 TiB 50% VS1 vdisk set map memory per server node class available required required per vdisk set ---------- --------- -------- ---------------------- nc1 10 GiB 3633 MiB VS1 (48 MiB)
- Check the file systems status.
- Check pdisk installation in the new nodes.
After importing a filesystem, it is recommended to check that the drives were migrated to the correct nodes. Use the eceimportpdiskcheck validate command to verify whether the disks are installed correctly.
- An example of correctly installed pdisks
# eceimportpdiskcheck validate eceimportpdiskcheck: Drives are inserted correctly on all nodes and recovery groups eceimportpdiskcheck: Done
- An example of misplaced pdisks
# eceimportpdiskcheck validate eceimportpdiskcheck: The following pdisks need renaming (rg:node:currentName:newName): eceimportpdiskcheck: rg1:c72f3u25-eth0:n001p001:n003p001 eceimportpdiskcheck: rg1:c72f3u25-eth0:n001p002:n003p002 eceimportpdiskcheck: rg1:c72f3u25-eth0:n001p004:n003p004 eceimportpdiskcheck: rg1:c72f3u25-eth0:n001p003:n003p003 eceimportpdiskcheck: rg1:c72f3u27-eth0:n003p002:n001p002 eceimportpdiskcheck: rg1:c72f3u27-eth0:n003p004:n001p004 eceimportpdiskcheck: rg1:c72f3u27-eth0:n003p003:n001p003 eceimportpdiskcheck: rg1:c72f3u27-eth0:n003p001:n001p001
- An example of correctly installed pdisks
- Check the imported pdisks.
# eceimportpdiskcheck update eceimportpdiskcheck: The following pdisks need renaming (rg:node:currentName:newName): eceimportpdiskcheck: rg1:c72f3u25-eth0:n001p001:n003p001 eceimportpdiskcheck: rg1:c72f3u25-eth0:n001p002:n003p002 eceimportpdiskcheck: rg1:c72f3u25-eth0:n001p004:n003p004 eceimportpdiskcheck: rg1:c72f3u25-eth0:n001p003:n003p003 eceimportpdiskcheck: rg1:c72f3u27-eth0:n003p002:n001p002 eceimportpdiskcheck: rg1:c72f3u27-eth0:n003p004:n001p004 eceimportpdiskcheck: rg1:c72f3u27-eth0:n003p003:n001p003 eceimportpdiskcheck: rg1:c72f3u27-eth0:n003p001:n001p001 eceimportpdiskcheck: Updating scale-out pdisk names eceimportpdiskcheck: Updating RG Status ... eceimportpdiskcheck: Done
- Verify the imported pdisks
again.
A sample output is as follows:# eceimportpdiskcheck validate
eceimportpdiskcheck: Drives are inserted correctly on all nodes and recovery groups eceimportpdiskcheck: Done
Important: The import steps may encounter failures if certain system state checks are not met. Review the command output for guidance on resolving any issues. If problems persist reach out to IBM support for assistance.