- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
- API Reference
- SDK Reference
- Troubleshooting
-
FAQs
- Concepts
- Specifications
- Restrictions
- Networks
- Billing
-
Others
- How Do I Access a File System from a Server?
- How Do I Check Whether a File System on a Linux Server Is Available?
- What Resources Does SFS Occupy?
- Can a File System Be Accessed Across Multiple AZs?
- How Can I Migrate Data Between SFS and EVS?
- Can I Directly Access SFS from On-premises Devices?
- How Do I Delete .nfs Files?
- How Can I Improve the Copy and Delete Efficiency with an SFS Turbo File System?
- How Do Second- and Third-level Directory Permissions of an SFS Turbo File System Be Inherited?
Show all
Viewing a File System
You can search for file systems by file system name keyword and view their basic information.
Procedure
- Log in to the SFS console.
- In the file system list, view the file systems you have created. Table 1 describes the file system parameters.
Table 1 Parameter description Parameter
Description
Name
Name of the file system, for example, sfs-name-001
Status
Possible values are Available, Unavailable, Frozen, Creating, Deleting.
Type
File system type
Protocol Type
File system protocol, which is NFS
Used Capacity (GB)
File system space already used for data storage
NOTE:
This information is refreshed every 15 minutes.
Maximum Capacity (GB)
Maximum capacity of the file system
Encrypted
Encryption status of the file system. The value can be Yes or No.
Enterprise Project
Enterprise project to which the file system belongs
Mount Point
File system mount point, which is in the format of File system IP address:/
Operation
For an SFS Turbo file system, valid operations include capacity expansion, deletion, monitoring metric viewing, subscription renewal, and unsubscription.
- (Optional) Search for the specified file system by file system name.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
