Re: Problem - After a reboot, the *first* `mount -a -t nfs' gets stuck in `D'
Jussi Silvennoinen <[email protected]>
| Newsgroups | gmane.linux.redhat.release.taroon.general |
|---|---|
| Message-ID | <[email protected]> |
> Running Red Hat Enterprise Linux AS release 3 (Taroon Update 8) > > Kernels - on one box tired 2.4.21-47.EL 2.4.21-40.EL and 2.4.21-37.0.1.EL > on another 2.4.21-40.ELsmp > > Hardware - IBM 1U rack mounted boxes (x-305 iirc) > Intel(R) Pentium(R) 4 CPU 1.80GHz > > Last night something happened - A network event possibly. Since then: > > On attempting to reboot my machines they fail to come up all the way. > They stop in netfs. They do come up all the way if I `chkconfig netfs off'. > > *BUT* if I then log in and type > mount -a -t nfs & > the mount process hangs - in state D. > > However if I type > mount -a -t nfs & > *again* this time it succeeds quite normally. Disks are mounted. All > is well. > > This has been seen on two machines so far. > > The first mount process is still in D: > > # ps auxww | grep mount > root 1880 0.0 0.0 3776 812 pts/0 D 10:48 0:00 mount -a -t nfs > root 2532 0.0 0.0 3688 672 pts/0 S 11:18 0:00 grep mount Do you have 'bg' in fstab for that mount? Try 'ps xal' and see what's it doing. -- Jussi -- Taroon-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/taroon-list