We are seeing nfsd getting stuck in d wait at boot time. The fix seems
to be stopping in single user mode prior to nfs starting, renaming
/var/lib/nfs/v4recovery/ and making a new one, then letting the system
continue. When it boots and hangs, all processes that touch
/var/lib/nfs/v4recovery/ go into D-wait. However, if you rename it and
let it boot you can look in the old directory. Any ideas what could be
happening?
Also, is there any documentation on the files in
/var/lib/nfs/v4recovery/? We would like to possibly be able to decode
the names.
begin:vcard
fn:David Warren
n:Warren;David
org:Atmospheric Sciences
adr:Dept of Atmospheric Sciences, Box 351640;;University of Washington;Seattle;WA;98195-1640;USA
email;internet:warren@xxxxxxxxxxxxxxxxxxxx
title:Software Engineer
tel;work:206 543-0945
url:http://www.atmos.washington.edu
version:2.1
end:vcard
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
NFS maillist - NFS@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@xxxxxxxxxxxxxxxxxxxxx is being discontinued.
Please subscribe to linux-nfs@xxxxxxxxxxxxxxx instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
