Re: Problem - After a reboot, the *first* `mount -a -t nfs' gets stuck in `D'
Keith Lewis <keithl-t1tvXobVCYWi/[email protected]>
| Newsgroups | gmane.linux.redhat.release.taroon.general |
|---|---|
| Message-ID | <[email protected]> |
RE: > > 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? Yes. One of our two failing machines has two NFS mounts, both from a NFS server serving a pair of GFS disks. The other client has three mounts - one from a nearby NFS server which serves its own hard disk, the other two are the same GFS via NFS as above. BUT - commenting out the GFS via NFS mounts on the second box did not fix the problem. (i.e. this problem appears not to be GFS related) They are `bg' in all cases e.g. # grep /web/nfs /etc/fstab <name>:/web/canon /web/nfs nfs rw,bg,hard,intr,nodev,nosuid 0 0 # > Try 'ps xal' and see what's it doing. # ps axl F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND ... 4 0 1880 1822 15 0 3776 812 end D pts/0 0:00 mount -a -t nfs > -- > Jussi Keith -- Taroon-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/taroon-list