Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Scalable File Service/ Getting Started/ Mount a File System/ Mounting an NFS File System to ECSs (Windows)

Mounting an NFS File System to ECSs (Windows)

Updated on 2024-11-15 GMT+08:00

After creating a file system, you need to mount it to ECSs so that they can share the file system.

This section uses Windows Server 2012 as the example OS to describe how to mount an NFS file system. For other versions, perform the steps based on the actual situation.

An SFS Capacity-Oriented file system can use either the NFS or CIFS protocol. It cannot use both protocols.

In this section, ECSs are used as example servers. Operations on BMSs and containers (CCE) are the same as those on ECSs.

Prerequisites

  • You have created a file system and have obtained its mount point.
  • At least one ECS that is in the same VPC as the file system is available.
  • The IP address of the DNS server for resolving the file system domain name has been configured on the ECSs. For details, see Configuring DNS.

Notes and Constraints

You are advised to use CIFS file systems in Windows OS.

SFS Turbo file systems cannot be mounted to Windows ECSs.

General purpose file systems cannot be mounted to Windows ECSs.

Procedure

  1. Go to the ECS console and log in to the ECS running Windows Server 2012.
  2. Install the NFS client.

    1. Click Server Manager in the lower left corner to open Server Manager, as shown in Figure 1.
      Figure 1 Server Manager
    2. Click Add roles and features.
      Figure 2 Wizard for adding roles and features
    3. Click Next as prompted. On the Server Roles page, select Server for NFS.
      Figure 3 Selecting Server for NFS
    4. Click Next. On the Features page, select Client for NFS and click Next. Confirm the settings and then click Install. If you install the NFS client for the first time, after the installation is complete, restart the client and log in to the ECS again as prompted.
      Figure 4 Selecting Client for NFS

  3. Modify the NFS transport protocol.

    1. Choose Control Panel > System and Security > Administrative Tools > Services for Network File System (NFS).
      Figure 5 Administrative tools
    2. Right-click Client for NFS, choose Properties, change the transport protocol to TCP, and select Use hard mounts.
      Figure 6 Services for NFS
      Figure 7 Client for NFS properties

  4. Check that the IP address of the DNS server for resolving the file system domain name has been configured on the ECS before mounting the file system. For details, see Configuring DNS. SFS Turbo file systems do not require domain name resolution.
  5. Run the mount command in the Command Prompt of the Windows Server 2012 (X is a free drive letter). Select the ECS that is in the same VPC as the file system to mount the file system.

    For SFS Capacity-Oriented file systems: mount -o nolock Mount point X:

    NOTE:
    • A free drive letter is one that is not in use, such as drive letter E or X.

    You can move the cursor to the mount point and click next to it to copy the mount point. For details, see Figure 8. If the information shown in Figure 9 is displayed, the mount is successful.

    Figure 8 Mount point

    Figure 9 Running the command

  6. After the file system is mounted successfully, view the mounted file system in the This PC window.

    If the mount fails or times out, rectify the fault by referring to Troubleshooting.

    Figure 10 Successful mount
    NOTE:

    To distinguish different file systems mounted on an ECS, you can rename file systems by right-clicking a file system and choose Rename.

Troubleshooting

If a file system is mounted to a Linux ECS and a Windows ECS, on the Windows ECS, you cannot write data to the files created by the Linux ECS. To address this problem, modify the registry to change both UID and GID values to 0 for NFS accesses from Windows. This section uses Windows Server 2012 as an example. Do as follows:

  1. Choose Start > Run and enter regedit to open the registry.
  2. Enter the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default directory.

    Figure 11 Entering the directory

  3. Right-click the blank area and choose New > DWORD Value from the shortcut menu. Set AnonymousUid and AnonymousGid to 0. Figure 12 shows a successful operation.

    Figure 12 Adding values

  4. After the registry is modified, restart the server for the modification to take effect.

Usamos cookies para aprimorar nosso site e sua experiência. Ao continuar a navegar em nosso site, você aceita nossa política de cookies. Saiba mais

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback