Client Specifications and Limits
Last updated: 2025-07-17 17:16:40
This document describes the specifications and limitations of the GooseFSx POSIX client.
Applicable Operating Systems
The POSIX client of GooseFSx supports Linux and Windows operating systems. The recommended operating system versions are as shown in the table below:
Operating System Types | Operating System | Edition | Kernel version |
Linux | TencentOS Server | TencentOS Server 3.1 (TK4) | Deeply optimized based on the community 5.4 LTS kernel |
| | TencentOS Server 2.4(TK4) | Deeply optimized based on the community 5.4 LTS kernel |
| RHEL or CentOS | 8.4 | 4.18.0-305.19.1.el8_4 |
| | 8.3 | 4.18.0-240.22.1.el8_3 |
| | 8.2 | 4.18.0-193.28.1.el8_2 |
| | 8.1 | 4.18.0-147.8.1.el8_1 |
| | 8 | 4.18.0-80.11.2.el8_0 |
| | 7.9 | 3.10.0-1160.42.2.el7 |
| | 7.8 | 3.10.0-1127.19.1.el7 |
| | 7.7 | 3.10.0-1062.18.1.el7 |
| | 7.6 | 3.10.0-957.54.1.el7 |
| | 7.5 | 3.10.0-862.14.4.el7 |
| | 7.4 | 3.10.0-693.2.2.el7 |
| | 7.3 | 3.10.0-514.26.2.el7 |
| | 7.2 | 3.10.0-514.26.2.el7 |
| Ubuntu | Ubuntu 22.04 | 5.15.0-27-generic |
| Ubuntu | Ubuntu 20.04 | 5.4.0-147-generic |
Windows | Windows | Windows 2016 | all |
| | Windows 2019 | all |
Note:
If your operating system version is not listed in this table, you can consult online customer service for help.
POSIX Client Specification
Project | Specification | Description |
Single GooseFSx instance supports POSIX client count | 4096 | A single GooseFSx instance can be mounted by 4096 POSIX clients simultaneously. |
Number of GooseFSx instances that a single POSIX client can mount | 1 | A single POSIX client can only mount one GooseFSx instance. Note: Since unmounting by the client is an asynchronous operation and takes some time to complete completely. Therefore, it takes more than 10 minutes for a POSIX client to unmount a GooseFSx instance before it can be remounted; otherwise, mounting fails. |
Minimum configuration for a POSIX client | 4 core 8 GB | Recommended minimum configuration for a POSIX client: 4 cores, 8GB memory. The available memory space of the client must be greater than 2GB to avoid deployment failure caused by insufficient available memory. |
Note:
If this table cannot meet your needs or you have other requirements, you can consult online customer service for help.
Do not delete or overwrite the authorized_keys file of the POSIX client. Recommend using the
ssh copy command to append write the authorized_keys file. Do not use the scp command to overwrite write the authorized_keys file.POSIX Client Security Group Rules
The POSIX client needs to allow the following ports to communicate with GooseFSx. For relevant guidelines, please see Configure Security Group. If you also set up a security group with a denial policy for the POSIX client, please ensure that the POSIX client security group rules are not denied.
Protocol | Direction | Port | IP |
TCP | inbound rule | 22,1191,4242,4243,4739,8445,9085,9250,9251,9980,10080,55533,60000-61000 | All IPs in the VPC to which GooseFSx belongs |
UDP | inbound rule | 4739 | All IPs in the VPC to which GooseFSx belongs |
ICMP | inbound rule | ALL | All IPs in the VPC to which GooseFSx belongs |
Note:
Port 22 is the default port number used for SSH mutual trust communication between the POSIX client and the client management node. If it does not meet your requirements, customization is supported, and available ports can avoid the TCP ports allowed by the POSIX client's security group rules.
For example, if you customize the port to 2008, 22 will be replaced with 2008 and appear in the POSIX client security group rule.
GooseFSx Occupied VPC Subnet IP Address
To enable communication between hosts in the Customer VPC and GooseFSx, the GooseFSx file system will occupy a certain number of IP addresses in the VPC subnet. The larger the GooseFSx capacity, the more IP addresses are occupied, as follows:
Model | Number of Occupied IP Addresses | Description |
C50.T3 | 1 IP address per 3 TiB | 9 TiB capacity occupies 3 IPs |
C50.T12 | 1 IP address per 12 TiB | 36 TiB capacity occupies 3 IPs |
C60.T2 | 1.5 TiB uses 1 IP address | 4.5 TiB capacity occupies 3 IPs |
C60.T12 | 1 IP address per 12 TiB | 36 TiB capacity occupies 3 IPs |
C70 | 1 IP address per 4.65 TiB | 13.95 TiB capacity occupies 3 IPs |
Note:
If the available IP addresses in this VPC are insufficient, it can cause GooseFSx expansion or creation failure. You can consult online customer service to ask for help.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback