Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I would guess it means that on the last reboot of the NFS server, the Slackware server was unable to reclaim it's file locks because it has it's grace period set to a negative integer (-110), so the grace period effectively never runs out because it cannot be accurately evaluated.
However that's just a guess
"cat" these three files on the Slackware server (they're in /proc/sys so they are being exported from kernel-space don't try to open them in an editor or you'll get an unpleasant surprise.)
If one of them is set to '-110' or any other non-standard value (i.e. it doesn't match the other two)...
Stop NFSD
Echo the same value into all three (30 is 30 seconds, for example. If you're unsure what value to set, check one of the other Linux clients that are mounting NFS to see what values they are set to and use that).
Restart NFSD and see if that resolves the issue.
Since the contents of /proc are entirely synthetic ... it is actually a kernel API, not any sort of physical resource ... I conclude that the NFS subsystem, although provided-for in the kernel, is not running.
On VMs which use NFS shares, I see that this directory exists and is populated.
On VMs which do not use NFS, I see that the directory exists ... somewhat to my surprise ... but is empty.
Since the contents of /proc are entirely synthetic ... it is actually a kernel API, not any sort of physical resource ... I conclude that the NFS subsystem, although provided-for in the kernel, is not running.
But, it must be running or client machines could not see the NFS exported directories.
Quote:
On VMs which use NFS shares, I see that this directory exists and is populated.
On VMs which do not use NFS, I see that the directory exists ... somewhat to my surprise ... but is empty.
Not sure what you're saying here. What do you mean by "VM's"? Virtual Machines? I have not virtual machines in the mix. The /proc/fs/nfsd directory is empty on my NFS client. It is also empty on hosts that do not use NFS.
The /proc/fs/nfsd directory is empty... on hosts that do not use NFS.
That makes sense
I think the confusion lies here.
The Slackware machine is an NFS client, not the NFS server. TRUE/FALSE
IF TRUE
Other nodes with a fully functional NFS kernel drivers should be able to mount any directory exported from the NFS server assuming they are authorized to do so in the NFS servers exports configuration on the NFS server. The Kernel driver on the Slackware client seems to have at least partially failed and therefor cannot "recapture" it's NFS mounts because the 'grace-period' where is delays accessing the mounts to allow the Server to clear the pre-existing file locks never expires (because the mechanism at the kernel level it is relying on doesn't exist).
IF FALSE
Why are you trying to mount local NFS shares onto the NFS server? These shares are already running locally through the mounted file system? It seems an unlikely thing to do and so was discounted in the initial discussion.
That makes sense
I think the confusion lies here.
The Slackware machine is an NFS client, not the NFS server. TRUE/FALSE
Yes, confusion. Let me try to clarify. I have several computers, all Linux. For the case in point, one of them is an NFS server exporting a couple of directories, let's call it "A". It is this server that is getting the "NFSD: Unable to end grace period: -110". I have a client, "B" who mounts an exported directory of A's. I reported that, despite the error on A, B can mount A's export.
But now, you make me question myself on this. Due to another problem, I have temporarily switch motherboard and CPU on server A and, interestingly, have not see this error since, so cannot at this time verify that B can mount A's exports. I will be putting the hardware back the way is was in the next 24 hours, so I'll double check this and report back.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
