-
Notifications
You must be signed in to change notification settings - Fork 9
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
restarting NFSRODS without re-mounting at the client produces incorrect behavior #46
Comments
We've seen similar behavior, but have not been able to pin it down. We're currently thinking it might be on the mount (with caching?) side of things. Any insight is welcome. |
need to retest - this could have been fixed by f410957? |
I believe using the DATA_ID as the file handle will resolve this issue. Will investigate. |
I see similar symptoms occasionally here:
This is nfsrods 2.1.0 on Ubuntu 18.04 for both the NFS client and nfsrods server. I have nfsrods debug logs for this if that's useful. |
We've been focused on getting 4.2.12 released, so this issue has taken a backseat to that. We will take care of this as soon as we can. |
FYI @davebiffuk is one of my fine Sanger colleagues. |
- Uses the object ID of collections and data objects as the inode number - Provides a lookup for cache misses on previously encountered object IDs to generate logical paths
- Uses the object ID of collections and data objects as the inode number - Provides a lookup for cache misses on previously encountered object IDs to generate logical paths
Excellent work @ganning127! Closing! |
If I start NFSRODS and mount, I can see the VFS correctly with
ls
.But if I restart NFSRODS without re-mounting, I often get incorrect and inconsistent behavior.
Note in the last example that the directories were returned and reported "No such file or directory."
This behavior seems to resolve itself after a short time.
The text was updated successfully, but these errors were encountered: