[opensuse] Filesystems not unmounted during shutdown
Hello list, I recently had to get rid of the boot splashscreen on my home server. Meaning that I now get to see the console boot messages each time, and I noticed something quite alarming: an fsck and a transaction log replay takes place each time the server boots, even though I take great care to always shut it down cleanly. Watching the console during shutdown or browsing the logs, I couldn't find anything indicating failure. My guess, at this stage, is that the script that should unmount the filesystems (/etc/init.d/boot.localfs) is either never called or no doing anything for some reason. Peter Nikolic already reported a similar behaviour on this list a few months ago, and filed a bug about it: <https://bugzilla.novell.com/show_bug.cgi?id=626580> Peter experienced this problem on 11.3 (and for a single filesystem). I'm seeing this on 11.2, and for all the filesystems on the server. We're both using reiser on at least some of our filesystems (is there a link ?). If anyone else has had the same problem, could they please feed more information into the above bug ? Or provide a solution if they have one ? TIA Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com <http://www.iba-worldwide.com>
Philippe Andersson said the following on 09/09/2010 10:17 AM:
Hello list,
I recently had to get rid of the boot splashscreen on my home server. Meaning that I now get to see the console boot messages each time, and I noticed something quite alarming: an fsck and a transaction log replay takes place each time the server boots, even though I take great care to always shut it down cleanly.
Yes, so? You don't say what file system. My ReiserFS do that on every boot regardless. Following a clean shutdown I see the reboot saying Replaying journal: Done. Its the nature of the reiser.fsck that runs at boot. There's nothing "in" the journal to reply, because there was a clean shutdown. Now if you get a long list of what is being replayed then you know that your shutdown wasn't really clean, that the file system wasn't properly unmounted. If that's the case then you should investigate WHY the file system isn't being properly unmounted on shutdown. -- If a better system is thine, impart it; if not, make use of mine. - Horace -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anton Aylward wrote:
Philippe Andersson said the following on 09/09/2010 10:17 AM:
Hello list,
I recently had to get rid of the boot splashscreen on my home server. Meaning that I now get to see the console boot messages each time, and I noticed something quite alarming: an fsck and a transaction log replay takes place each time the server boots, even though I take great care to always shut it down cleanly.
Yes, so?
You don't say what file system. Quoting from memory: / (reiser) /boot (ext2) /home (reiser) /data (reiser)
My ReiserFS do that on every boot regardless. Following a clean shutdown I see the reboot saying
Replaying journal: Done. I see hundreds of log entries being applied in addition to that message. Please correct me if I'm wrong, but I don't think that's normal behaviour after a supposedly clean shutdown.
Its the nature of the reiser.fsck that runs at boot.
Sure.
There's nothing "in" the journal to reply, because there was a clean shutdown. In my case there is. Every time.
Now if you get a long list of what is being replayed then you know that your shutdown wasn't really clean, that the file system wasn't properly unmounted.
That was my whole point -- my apologies that it wasn't clear enough. The server is always shutdown properly, either from the KDM menu entries or from the command-line.
If that's the case then you should investigate WHY the file system isn't being properly unmounted on shutdown.
That's the aspect of the question being discussed in the bug I referred to (and commented on). Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com <http://www.iba-worldwide.com>
Philippe Andersson said the following on 09/09/2010 10:42 AM:
There's nothing "in" the journal to reply, because there was a clean shutdown. In my case there is. Every time.
Now if you get a long list of what is being replayed then you know that your shutdown wasn't really clean, that the file system wasn't properly unmounted.
That was my whole point -- my apologies that it wasn't clear enough. The server is always shutdown properly, either from the KDM menu entries or from the command-line.
If that's the case then you should investigate WHY the file system isn't being properly unmounted on shutdown.
That's the aspect of the question being discussed in the bug I referred to (and commented on).
I would suggest, then. doing a shut-down like this. a) do an 'init 3' to get out of the DM mode. b) one by one, unmount the file systems You will find you can't because of running processes Identify what those are with 'fuser' Item (b) is easier for me 'cos I have lots of file systems /usr /usr/share /usr/share/doc /use/lib /home/anton/Documents ..... /tmp /opt Running LVM makes this a lot easier :-) Of course this gives me practice in tracking down file system problems since I have less-than-critical ones to c) do an 'init 1' You should now have none of those processes :-) Try un-mounting. Then mounting again. This isn't a 'cure', its just to give more insight into what's going on. I'm not proposing it as a normal form of shut-down, but just so you can investigate what is happening. Personally, I think your file systems are overloaded. There are some security issues (go google) with having the /tmp on the same FS as /bin and /sbin. Its also useful so you don't get an aberrant processes filling up /tmp=/ and freezing your system. -- "If I must write the truth, I am disposed to avoid every assembly of bishops; for of no synod have I seen a profitable end, but rather an addition to than a diminution of evils; for the love of strife and the thirst for superiority are beyond the power of words to express." -- Father Gregory Nazianzen, 381 AD -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 9/9/2010 11:16 AM, Anton Aylward wrote:
Philippe Andersson said the following on 09/09/2010 10:42 AM:
There's nothing "in" the journal to reply, because there was a clean shutdown. In my case there is. Every time.
Now if you get a long list of what is being replayed then you know that your shutdown wasn't really clean, that the file system wasn't properly unmounted.
That was my whole point -- my apologies that it wasn't clear enough. The server is always shutdown properly, either from the KDM menu entries or from the command-line.
If that's the case then you should investigate WHY the file system isn't being properly unmounted on shutdown.
That's the aspect of the question being discussed in the bug I referred to (and commented on).
I would suggest, then. doing a shut-down like this.
I'm pretty sure Philippe knows how to manually shutdown each file system. That's hardly the point. What He reporting is clearly a bug, and one seen and filed previously, with no resolution. -- _____________________________________ At one time I had a Real Sig. Its been downsized. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Anton Aylward -
John Andersen -
Philippe Andersson