Bug#2459: Filesystems unmounted in wrong order
You (Andrew Howell) wrote:
> Package: sysvinit
> Version: 2.58-2
>
> Rob Leslie writes:
> >
> > >> Do you have any NFS partitions mounted under /var when you shutdown or
> > >> reboot?
> > >
> > > Yes, /var/spool/mail.
> >
> > Please see my Bug#2304. The problem is that during shutdown, the network layer
> > (e.g. PPP?) is destroyed before any attempt is made to unmount the NFS
> > partition, which subsequently fails. This also leaves /var unable to be
> > unmounted, which is why you see it being fscked on reboot.
> >
> > I have not yet seen any suggestions for how to resolve this problem. If you
> > have any ideas, I would welcome a discussion.
>
> The problem seems to be in /etc/init.d/reboot at these lines.
>
> echo -n "Unmounting file systems... "
> umount -a -tnonfs 2>/dev/null
> umount -a -tnfs 2>/dev/null
>
> I think these should be around the other way as it's causing my /var
> partition to not umount cause /var/spool/mail is still mounted when
> it tries to unmount /var.
I have changed that in 2.59, so it should be allright now.
> Is there any reason why nfs mounted filesystems should be unmounted
> after every other type of filesystem?
Yes, if you want to reboot because something is wrong with the network
and it hangs on unmounting the NFS disks your screwed. But I now
think umount should handle this (with a timeout of say 10 seconds on NFS
mounts) instead of the halt/reboot script.
Mike.
--
Miquel van | Cistron Internet Services -- Alphen aan den Rijn.
Smoorenburg, | mailto:info@cistron.nl http://www.cistron.nl/
miquels@het.net | Tel: +31-172-419445 (Voice) 430979 (Fax) 442580 (Data)
Reply to: