On 01/30/2011 02:11 PM, JB wrote:
JB<jb.1234abcd<at> gmail.com> writes:
>
> # ################################################################
> # debugging snapshot statements
> # ----------------------------------------------------------------
> date>> /halt.debug
> cat /etc/mtab>> /halt.debug
> cat /proc/mounts>> /halt.debug
> # ################################################################
>
I think correction is needed as /proc is not available any more because it
was unmounted immediatelly prior to our debugging statements.
So, remove that:
cat /proc/mounts>> /halt.debug
JB
I added the debug, and basically it was the same when it shutdown cleanly
and when it failed.
# A bad one
Sun Jan 30 17:12:08 GMT 2011
/dev/sda1 / ext4 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
Mount:
/dev/sda1 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
fstab-decode mount -n -o ro,remount /dev/sda1 /
fstab-decode mount -n -o ro,remount proc /proc
fstab-decode mount -n -o ro,remount sysfs /sys
# A good one, / has been remounted ro and so the last two unmount messages are
not present
Sun Jan 30 17:18:16 GMT 2011
/dev/sda1 / ext4 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
Mount:
/dev/sda1 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
fstab-decode mount -n -o ro,remount /dev/sda1 /
I put a /bin/sh after this so I could have a look at the systems state at this
point when the remount failed. The last few items of the "ps ax" list is shown:
1282 ? S 0:00 [rpciod/1]
1378 ? S 0:00 [nfsiod]
1381 ? S 0:00 [lockd]
1960 ? D 0:00 [flush-0:19]
2006 ? Zl 0:00 [akonadi_control] <defunct>
2008 ? Z 0:00 [akonadiserver] <defunct>
2010 ? Zl 0:00 [mysqld] <defunct>
2125 ? Ds 0:00 [pulseaudio]
2332 ? Z 0:00 [gconf-helper] <defunct>
2365 ? D 0:00 [dcopserver]
2448 ? Ss 0:00 /bin/bash /etc/rc0.d/S01halt start
3001 ? S 0:00 /bin/sh
3019 ? R 0:00 ps ax
It looks like some processes are left over from the GUI (KDE).
I suspect they have log files or something else opened on /
in write mode and this is stopping the remount to ro working.
Running "mount -o remount,ro /" at this point fails with "/ is busy".
They are probably waiting for /home, which is an NFS files system, that
was unmounted earlier on in the shutdown process.
I restarted the network and netfs and these processes disappeared. After
shuting down netfs and network as well as some other processes left over
the remount command worked fine and the system shutdown.
Note I am using the "network" not "NetworkManager" service. The
NetworkManager
service does not work well for me with systems using networked /home and
other file systems.
I suspect an issue further up the shudown chain where the system should
wait for all of the processes to shutdown "before" unmounting the NFS files
systems. I will have a look here, any ideas ?
Terry