- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Billing
- Getting Started
- User Guide
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
API
- Lifecycle Management
- Connection Management
- Tag Management
- Name Management
- File System Management
-
Storage Interworking Management
- Adding a Backend Target
- Querying Backend Targets
- Obtaining Details About a Backend Target
- Deleting a Backend Target
- Updating the Properties of a Storage Backend
- Updating the Auto Synchronization Policy of a Storage Backend
- Creating an Import or Export Task
- Querying Details About an Import or Export Task
- Listing Import and Export Tasks
- Deleting an Import or Export Task
- Updating a File System
- Directory Management
-
Permissions Management
- Creating a Permission Rule
- Querying Permission Rules of a File System
- Querying a Permission Rule of a File System
- Modifying a Permission Rule
- Deleting a Permissions Rule
- Creating and Binding the LDAP Configuration
- Querying the LDAP Configuration
- Modifying the LDAP Configuration
- Deleting the LDAP Configuration
- Task Management
- Permissions Policies and Supported Actions
- Common Parameters
- Appendix
- SDK Reference
-
FAQs
- SFS Turbo Concepts
- SFS Turbo Specifications
- SFS Turbo Billing
-
SFS Turbo Mount
- What Can I Do If Data of My SFS Turbo File System Is Not the Same When Accessed from Two Client Servers?
- Can I Mount an SFS Turbo File System Across Regions?
- Can I Mount an SFS Turbo File System Across Accounts?
- How Many Cloud Servers Can I Mount an SFS Turbo File System To?
- How Do I Mount a File System to a Linux ECS as a Non-root User
- What Can I Do If Mounting a Subdirectory of a File System Failed?
- SFS Turbo Access
- SFS Turbo Capacity Expansion
- SFS Turbo Deletion
- SFS Turbo Migration
- SFS Turbo Performance
-
Others
- Does the Security Group of a VPC Affect the Use of SFS Turbo?
- What Resources Does SFS Turbo Occupy?
- How Do I Check Whether an SFS Turbo File System Is Available on a Linux Server?
- Can I Upgrade an SFS Turbo File System from the Standard Type to the Performance Type?
- Does SFS Turbo File Systems Support Multi-AZ Deployment?
-
Troubleshooting
- Mounting a File System Timed Out
- Mounting a File System Failed
- File System Performance Was Poor
- Creating an SFS Turbo File System Failed
- File System Automatically Unmounted
- A Client Server Failed to Access a File System
- Abnormal File System Status
- Data Fails to Be Written into a File System Mounted to ECSs Running Different Types of Operating Systems
- Writing to a File System Failed
- Error Message "wrong fs type, bad option" Was Displayed During File System Mounting
- General Reference
Copied.
How Do I Mount a File System to a Linux ECS as a Non-root User
Scenarios
By default, a Linux ECS allows only the root user to use the mount command to mount file systems, but you can grant the permissions of user root to other users. Such users can then use the mount command to mount file systems.
The following describes how to grant a non-root user the root permissions and how to mount a file system to a Linux ECS using that non-root user. EulerOS is used in this example.
Mounting a File System as a Non-root User
- Log in to the ECS as user root.
- Assign the root permissions to a non-root user.
- Run chmod 777 /etc/sudoers to make the sudoers file editable.
- Use the which command to view the mount and umount command paths.
Figure 1 Viewing command paths
- Run vi /etc/sudoers to edit the sudoers file.
- Add a user under root. In this example, user mike is added.
Figure 2 Adding a user
- Press Esc, enter :wq, and press Enter to save and exit.
- Run chmod 440 /etc/sudoers to make the sudoers file read-only.
- Log in to the ECS as user mike.
- Mount the file system. For details about the mount parameters, see Table 1.
sudo mount -t nfs -o vers=3,timeo=600,noresvport,nolock <Shared path> <Local path>
Table 1 Parameters required for mounting file systems Parameter
Description
<Shared path>
The format is <File system IP address>:/, for example, 192.168.0.0:/.
NOTE:
Variable x is a digit or letter.
If the shared path is too long to display completely, you can adjust the column width.
<Local path>
A local directory on the ECS used to mount the file system, for example, /local_path.
- View the mounted file system.
mount -l
If the command output contains the following information, the file system has been mounted:example.com:/share-xxx on /local_path type nfs (rw,vers=3,timeo=600,nolock,addr=)
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot