Run the following command to immediately process the /etc/fstab entries and attempt to mount the preceding path: mount /nfsdataįor a temporary mount that doesn't persist across reboots, run the following command: mount -t aznfs -o sec=sys,vers=3,nolock,proto=tcp. :// /nfsdata aznfs defaults,sec=sys,vers=3,nolock,proto=tcp,nofail,_netdev 0 0 To have the share mounted automatically on reboot:Ĭreate an entry in the /etc/fstab file by adding the following line. In both methods, replace the placeholder with the name of your storage account, and replace with the name of your container. Mount the container by using one of the following methods. On your Linux system, create a directory: mkdir -p /nfsdata Ubuntu (18.04 LTS, 20.04 LTS, 22.04 LTS)Ĭreate a directory on your Linux system and then mount the container in the storage account.Step 4: Create a containerĬreate a container in your storage account by using any of these tools or SDKs: ToolsĪZNFS is supported on following Linux distributions: You can accept the default values for all other settings. Public endpoint (selected networks) or Private endpoint Locally-redundant storage (LRS), Zone-redundant storage (ZRS) To configure the account, choose these values: Setting
For more information on these types of storage accounts, see Storage account overview. The NFS 3.0 protocol is supported for standard general-purpose v2 storage accounts and for premium block blob storage accounts. To mount a container by using NFS 3.0, you must create a storage account.
Step 3: Create and configure a storage account If you have granted access to specific VNets, make sure that any network security groups associated with those VNets don't contain security rules that block incoming communication through those ports. If you're connecting from an on-premises network, make sure that your client allows outgoing communication through those ports.
0 kommentar(er)
