Red Hat Bugzilla – Bug 169685
NFSD: recovery directory /var/lib/nfs/v4recovery doesn't exist
Last modified: 2013-01-09 22:39:19 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Fedora/1.7.12-1.5.1
Description of problem:
During bootup I am seeing this error messages:
Oct 1 05:05:46 mccallum kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Oct 1 05:05:46 mccallum kernel: NFSD: recovery directory /var/lib/nfs/v4recovery doesn't exist
Oct 1 05:05:46 mccallum kernel: NFSD: starting 90-second grace period
Googling for the subject seems to indicate this to be caused by the most recent kernel update (kernel-2.6.13-1.1526_FC4.i686), but I haven't investigated in depth.
I.e. I am not sure if this isn't a kernel bug, or an nfs-utils or an nfs-utils/kernel compatibility issue, nor am I sure about the effects stemming from this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Upgrade an FC4 system with nfs enabled to kernel-2.6.13-1.1526_FC4
Manually creating /var/lib/nfs/v4recovery seems to silence this warning.
nfs-utils-1.0.7-13.FC4 still doesn't have the missing /var/lib/nfs/v4recovery
directory added to the package.
The same problem exists on FC5 with nfs-utils-1.0.8.fc2-5.FC5. Can the
submitter or someone else with privs move the Version to fc5?
(In reply to comment #2)
> The same problem exists on FC5 with nfs-utils-1.0.8.fc2-5.FC5. Can the
> submitter or someone else with privs move the Version to fc5?
Still present in nfs-utils-184.108.40.206.fc5.
By the way, changing the version of FC is not that important. Getting the
maintainer of nfs-utils to look at this bug and fix it is more important.
fixed in nfs-utils-1.0.8-3.fc5
When is nfs-utils-1.0.8-3.fc5 actually going to be released to the repository?
Sorry about that... I guess I never added that version to the update que...
I have now....
hrmm, v4recovery directory needs to be added to the %files section.
Fixed in nfs-utils-1.0.8-4.fc5
Fix verified in FC5, FC6, F7. I suggest that this bug be closed.
*** Bug 189177 has been marked as a duplicate of this bug. ***
Closing as per comment #9.