Cloud Parallel File Storage:Mount a file system on a CPFS-POSIX client (Ubuntu/CentOS)

Step 1: Prepare the environment

Complete the following steps to prepare the environment before you install the CPFS-POSIX client.

Step 2: Configure the security group for the destination ECS instance

1. Obtain the security group information of the CPFS-POSIX control plane node ECS instance.

   1. Log on to the NAS console.

   2. In the navigation pane on the left, choose File System > File System List.

   3. In the upper-left corner of the page, select the resource group and region where the destination file system resides.

      

   4. Click the destination file system to go to its details page, and then click Mount Target.

   5. In the Client Management node section, click the ID of the first ECS instance in the list to open its details page.

   6. On the Instance Details page, click the Security Groups tab and record the Security Group ID/Name of the CPFS-POSIX control plane node.

      The name of the control plane node security group is in the format of <FSID>-<GENID>-qr-sg.

      <FSID> is the ID of the CPFS file system. <GENID> is the serial number of the mount target, which increments each time a CPFS mount target is created.

2. Add the security group of the CPFS-POSIX control plane node ECS instance to the destination ECS instance.

   1. In the navigation pane on the left, choose Instances & Images > Instances.

   2. On the Instances page, click the ID of the ECS instance on which you want to mount the CPFS file system. Click the Security Groups tab, and then click Change Security Group.

   3. In the Change Security Group dialog box, select the security group of the control plane node (<FSID>-<GENID>-qr-sg) that you recorded from the Security Group drop-down list, and then click Confirm.

Step 3: Mount the file system

1. Connect to the ECS instance where the CPFS-POSIX client is installed. For more information, see Select a tool to connect to an instance.

   You can find the ECS instance for the CPFS-POSIX client installation in the Client Management node section. The first ECS instance in the list is the default installation node. For more information, see View the information about a POSIX mount target.

2. Run the following command to install the CPFS-POSIX client on the destination ECS instances and add them to the client cluster.

   cpfs add <Internal IP address of destination ECS 1> <Internal IP address of destination ECS 2> <Internal IP address of destination ECS 3>

   Example:

   cpfs add 192.168.1.249 192.168.1.250 192.168.1.251

   Note

   • When you add ECS instances, enter their internal IP addresses.

   • Each client must have a unique hostname.

   • You can add one or more ECS instances. If you add multiple instances, separate their internal IP addresses with spaces.

   • The command execution time increases with the number of ECS instances that you add. It takes approximately 2 minutes to add a single ECS instance. We recommend that you run the command in the background using a tool such as screen or nohup.

3. Run the following command to confirm that the destination ECS instances are included in the node list.

   • Run the command

     mmlscluster

   • Sample output

      Node  Daemon node name                     IP address  Admin node name                      Designation
     ---------------------------------------------------------------------------------------------------------
        1   cpfs-001cb78****154e3-000001-qr-001  10.0.2.41   cpfs-001cb78****154e3-000001-qr-001  quorum-manager-perfmon
        2   cpfs-001cb78****154e3-000001-qr-002  10.0.2.43   cpfs-001cb78****154e3-000001-qr-002  quorum-manager-perfmon
        3   cpfs-001cb78****154e3-000001-qr-003  10.0.2.42   cpfs-001cb78****154e3-000001-qr-003  quorum-manager-perfmon
        4   iZbp11iqkys8rl5cwa4****              10.0.2.44   iZbp11iqkys8rl5cwa4****              perfmon

4. Optional: Query the default path.

   After you add the destination ECS instances to the client control plane node, the file system is automatically mounted to the default path /cpfs/<FSID serial number>. You can run the mmlsfs <FSID serial number>-<GENID> -T command to query the default path.

   • Sample command

     mmlsfs 001cb78****154e3-000001 -T

   • Sample output

     flag                value                    description
     ------------------- ------------------------ -----------------------------------
      -T                 /cpfs/001cb78****154e3-000001 Default mount point

   You can also run the mount --bind command to access the CPFS file system from a custom path.

   mount --bind /cpfs/001cb78****154e3-000001 /mnt/test

   /cpfs/001cb78****154e3-000001 is the default mount path of the CPFS file system. /mnt/test is the custom mount path.

   Note

   • Custom mount paths are not allowed on the CPFS file system installation node.

   • Subdirectory mounting is not supported.

   After the file system is mounted, you can access it in the same way you access a local directory.

FAQ

• What do I do if the "unsupported OS for 'X86_64' architecture" error is returned when I mount a CPFS file system?

• What do I do if the "make sure kernel-devel version is consistent with kernel" error is returned when I mount a CPFS file system?

• What do I do if the "ssh: connect to host A port 22: Connection timed out" error is returned when I mount a CPFS file system?

• What do I do if a YUM source error occurs when I run the cpfs add command to mount a CPFS file system?

• What do I do if the "[ FATAL ] No GPFS admin node specified. specify an admin node using 'spectrumscale node add -a'." error is returned when I mount a CPFS file system?

• How do I clear the residual configuration information of an uninstalled ECS instance?

• What do I do if the "[FATAL] B: Could not connect to B via ssh" error is returned when I mount a CPFS file system?

For more information about frequently asked questions (FAQs) and solutions for mounting CPFS, see Mounting and access FAQ.

References

• CPFS data streams

• Data monitoring

• Access control

• Uninstall a file system mounted using a CPFS-POSIX client