All Products
Search
Document Center

Cloud Parallel File Storage:Mount and access

Last Updated:Nov 11, 2025

This topic describes the clients and scenarios for mounting a file system. Review this topic before you mount a file system.

Client instructions

You can mount a CPFS file system using either a CPFS-POSIX client or a CPFS-NFS client. These clients are interoperable. For example, a file created by a CPFS-POSIX client and its modifications are visible to a CPFS-NFS client, and vice versa.

The CPFS-POSIX and CPFS-NFS clients have the following differences. Select a client to mount your CPFS file system based on your requirements.

  • Limits

    CPFS-POSIX client: The server where you mount the CPFS file system requires at least 2 CPU cores and 4 GiB of memory to operate correctly.

  • Supported Linux versions

    For more information about the Linux versions supported by the CPFS-POSIX and CPFS-NFS clients, see Limits.

  • Differences

    Differences

    CPFS-POSIX client

    CPFS-NFS client

    How to use

    Install the Portable Operating System Interface (POSIX) client package on the Linux compute node, and then add the compute node to the cluster.

    Install a lightweight Network File System (NFS) client. Then, run the mount command on the Linux system to mount and access the file system.

    Required mount target

    POSIX mount target.

    NFS endpoint of the protocol service (export directory).

    Support for K8s

    Container Storage Interface (CSI) in hostpath mode.

    CSI in NFS and hostpath modes.

    Quorum node

    Three small Quorum nodes are created on the client side, which incurs additional ECS fees.

    No Quorum nodes are created.

    Accessible space for the client

    The entire file system directory tree.

    The directory tree under the mount target.

    Performance

    Highest I/O access performance for data and metadata. Recommended for accessing small files under 100 KiB. For more information, see Specifications.

    The input/output operations per second (IOPS) for data and metadata is lower than that of the POSIX client due to the performance limits of the NFS protocol. Recommended for accessing data files of 100 KiB or larger. For more information, see Specifications.

    Access control

    NFSv4 access control lists (ACLs).

    NFSv4 ACLs that provide read-only and read/write control based on IP addresses and IP address ranges.

    Recommended scenarios

    ECS.

    Containers (K8s/ACK/ECI), special operating system versions, and video rendering.

Mounting scenarios

Mount a CPFS file system on an ECS instance

What to do next