![]() Review the NFS client logs (EC2 instance OS logs) under /var/log/messages for errors. ![]() Verify that the client can connect to the server by running the following command: telnet 2049 It's a best practice to use the current generation Linux NFS4v.1 client or later for better performance.ģ. If the kernel version is faulty, then upgrade the kernel. To confirm that the kernel version is the issue, verify the output from the ps command when you're unable to run ls: $ ps auxwwwm | grep If you're running one of these kernel versions, reboot to recover access to the file system. There might be issues with the particular kernel version, such as RHEL or CentOS 7.6 or later (kernel version of 3.10.0-957), that might cause the file system mount failure. For more information, see Recommended NFS mount options.Ģ. If you're using NFS to mount, then you must add this parameter explicitly. If you're using the EFS mount helper, then the noresvport option is present by default. Using noresvport makes sure that the EFS file system has uninterrupted availability after a network recovery event. This option makes sure that the NFS client uses the new TCP source port when a network connection must be reestablished. Use the noresvport mount option when mounting your file system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |