Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NFS4 initial command performance #22

Closed
ShahzadUmair opened this issue Feb 28, 2019 · 2 comments · May be fixed by #44
Closed

NFS4 initial command performance #22

ShahzadUmair opened this issue Feb 28, 2019 · 2 comments · May be fixed by #44

Comments

@ShahzadUmair
Copy link

The first command run on the mounted directory on client seems to take around a minute and a half to execute (touch hello.txt). All the commands run after the 1st command seems to execute normal. Do you happen to know what is causing this?

Docker run command:

docker run  --volume /data:/home --volume /tempData/exports.txt:/etc/exports:ro --privileged --env NFS_PORT=3001 -p 3001:3001 erichough/nfs-server

exports.txt

/home  *(rw,all_squash,anonuid=0,anongid=0,fsid=0)

Mount command

mount -o port=3001 -t nfs4 10.128.0.100:/ ./mnt

Interestingly enough, the 1st command runs normal when mounted as nfs3 (if i run server as nfs3 too).

@ShahzadUmair
Copy link
Author

I figured it out. It's the grace period causing the initial delay.

@ehough
Copy link
Owner

ehough commented Feb 28, 2019

Thanks for posting your resolution. I've never heard of the NFSv4 grace period. I'm going to see if there's a way that I can detect if the server is in the grace period and post a warning in the logs, just so others don't have to go through what you went through.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants