Scalable File Service
Scalable File Service
- 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?
On this page
Show all
Help Center/
Scalable File Service/
Best Practices/
Creating a Readable and Writable Subdirectory on the File System for a Common User/
Overview
Overview
Updated on 2022-09-16 GMT+08:00
Application Scenario
After a file system is created, only the root user has the read and write permissions on the file system by default. The root user can grant the access permission to multiple common users if needed. The root user can also create multiple subdirectories for each common user and mount them to the home directory of the file system, granting the read and write permissions to common users at the same time.
Procedure
Figure 1 illustrates the procedure of creating a readable and writable subdirectory on the file system for a common user.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.