search

Digital-Asset-Developer-Resources / aws

AWS required enviroment
GNU General Public License v3.0
0 stars 2 forks source link

Mounting NFS #4

Closed kenricnelson closed 4 years ago

kenricnelson commented 4 years ago

Tried to follow the AWS instructions for mount a file system; however, the command "sudo mount ..." timed out. Here are details. My understanding is that either the security group for NFS is not setup correctly or the DNS address is not correct.

Under the file system configuration, I followed the instructions in "Amazon EC2 mount instructions (from local VPC)"

"sudo apt-get install nfs-common" and "sudo mkdir efs" executed properly "sudo mount -t nfs4 -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport fs-00ebfa79.efs.us-east-2.amazonaws.com:/ efs" resulted in "connection time out"

The security guide under Amazon Elastic File Systems explained that a NFS Port 2049 connection is needed. Tried opening this port as both an addition to the existing security group and as a new security group just for the NFS connection.

Also tried the following command which uses the mount ip address "sudo mount -t nfs4 -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport 10.1.1.86:/ ~/efs"

Also tried 'starting' the nfs service with the command

"sudo service nfs start" resulted in "Failed to start nfs.service: Unit nfs.service not found."

kenricnelson commented 4 years ago

Resolved the issue by following the instructions at: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html

This mounted the disk using XFS. It also clarified that disk devices are under the /dev directory, the command "sudo mkfs -t xfs /dev/xvdb" is used to create the file system for the device, and that the command "sudo mount /dev/xvdb /data" is used to mount the disk within the file structure.