On Thu, 14 Apr 2011, Bastian Blywis wrote: > When /etc/init.d/reboot is run and "reboot -d -f -i" called, in about > 2-4% of the cases, the system will deadlock because the network > interfaces are shut down but the kernel still wants to read/write > something on the nfs export. The message "nfs server not responding" is > shown. > > Solutions: > 1) remove the "-i" from the init script > 2) move the parameters to /etc/default/reboot
Which can change wake-over-lan behaviour on various NICs, so it is not something we can do lightly. Although documenting this is a damn good idea. Really, all disk activity is supposed to be quiesced at this point, and everything is to be re-mounted read-only, so NFS should not need to do anything it cannot just give up on doing. Maybe that's where the real bug lies? Can you track down what is still mounted read-write at this point on your root-over-NFS boxes? Use /proc/mounts for this. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
