David Warren wrote:
> 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
(Cc fixed)
Can you get a Sysrq + w output by doing either
echo w > /proc/sysrq-trigger
(or)
Sysrq + w (hold Sysrq key and press 'w')
and capture dmesg output and attach?
It you could not get a shell, you could try to disable NFS during boot
and try to start NFS once the machine boots and then try.
Is the NFS server running inside a Virtual machine?
Thanks,
--
Suresh Jayaraman
------------------------------------------------------------------------------
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
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
