 | | | Problem - After a reboot, the *first* `mount -a -t nfs ' gets stuck in `D ' | Problem - After a reboot, the *first* `mount -a -t nfs ' gets stuck in `D ' 2006-09-06 - By Keith Lewis
Back
Its worse than I thought.
The reason we did the reboots yesterday was that
what appeard to be a network outage (lots of xterms vanished
from my workstation) had caused at least one NFS mount on
each of the two affected clients to `hang'. i.e. you type
`df' and you are hung in `D', or you type `ls /mount/point'
and you are stuck in D. (Hence the ampersands in my original
post). `umount -fl /mount/point ; mount /mount/point' seemed
to fix it but left heaps of processes on the machines stuck
in `D' and it was to get rid of them that we rebooted.
btw, these two machines are in a group of 10. None
of the others show this problem.
What makes things worse is that last night it all
happenned again! Those two machines, and only those two
machines, each lost one or two mounts, out of two or three,
and by this morning had heaps of processes stuck in `D'.
And even worse - this morning it wasn't the *second*
`mount -a -t nfs' that `fixed' it - but the third or fourth...
(One other thing that might be relevent, one of those
two boxes only found one of its two ethernets on this morning's
boot. For the moment, I'm assuming thats just an unrelated
hardware problem).
Any more clues gratefully accepted !!!
Keith
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
|