Expected behavior
Successfully able to edit files in EFS folders
Actual behavior
EFS mounted file can be seen, but when edit using an editor (e.g. vim), it getting stucked.
In kernel log, it says NFS server time out.
Additional Information
Used standard EFS mount options provided by AWS to mount EFS
Following logs can be seen in kern.log
kern.log:Feb 11 00:09:53 ip-172-21-0-171 kernel: nfs: server fs-6bf47b52.efs.ap-southeast-2.amazonaws.com not responding, still trying
kern.log:Feb 11 00:10:34 ip-172-21-0-171 kernel: [<ffffffffb22bcf98>] ? nfs_file_fsync+0x54/0x187
kern.log:Feb 11 00:12:37 ip-172-21-0-171 kernel: [<ffffffffb22bcf98>] ? nfs_file_fsync+0x54/0x187
kern.log:Feb 11 00:13:39 ip-172-21-0-171 kernel: nfs: server fs-6bf47b52.efs.ap-southeast-2.amazonaws.com not responding, timed out
kern.log:Feb 11 00:13:40 ip-172-21-0-171 kernel: nfs: server fs-6bf47b52.efs.ap-southeast-2.amazonaws.com not responding, timed out
kern.log:Feb 11 00:14:40 ip-172-21-0-171 kernel: [<ffffffffb22bcf98>] ? nfs_file_fsync+0x54/0x187
Steps to reproduce the behavior
- deploy the stack using https://editions-us-east-1.s3.amazonaws.com/aws/stable/Docker.tmpl ( Need EFS cloudstor plugin enabled)
- Attach a cloudstor EFS share and edit a file in the directory