https://bugzilla.novell.com/show_bug.cgi?id=450196
https://bugzilla.novell.com/show_bug.cgi?id=450196#c38
Jeff Mahoney changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |jeffm@novell.com
InfoProvider| |mrmazda@earthlink.net
--- Comment #38 from Jeff Mahoney 2011-02-09 19:18:53 UTC ---
Ok, we're going to need to rewind here. Coly was on the right track with fuser
-v, but didn't catch that it outputs the verbose parts to stderr.
There will still be quite a few things running like init, the shell it spawned
to execute the reboot, and any kernel threads. None of these things are
actually bad. It's how the system works.
Another important distinction is that the file system isn't actually unmounted
during shutdown/reboot - it's remounted read-only. It can't actually ever be
umounted since all kernel threads and init itself are using /. For archaic
reasons, umount output is redirected to /dev/null so that's why you're not
seeing errors. I think it's stupid to do that now.
So, the goal of the fuser -v is that it will display whether a file is opened
for writing. If there's a F in the third column, it's open for writing and will
prevent the file system from being remounted read-only.
So, see if this helps. If you want, you can redirect it to a file since the
file system will still be read-write.
Edit /etc/init.d/reboot to comment out:
mount -no remount,ro / 2> /dev/null
.. and add this:
if ! mount -no remount,ro /; then
fuser -vm / 2>&1 | grep F
sleep 10
fi
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.