https://bugzilla.novell.com/show_bug.cgi?id=642334 https://bugzilla.novell.com/show_bug.cgi?id=642334#c0 Summary: Root filesystem is not properly unmounted after reinstalling/updating basesystem Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vlukas@gmx.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.5; Linux) KHTML/4.5.1 (like Gecko) SUSE After larger Factory updates, when new basesystem components (Kernel, Init, aaa_base, etc...) are installed, on shutdown of the system the root filesystem is not unmounted successfully. When rebooting, a message stating this is shown and a filesystem check is done. A reliable way to reproduce this problem is to just reinstall the sysvinit package. Sometimes, it is possible to manually unmount the filesystem, by switching into runlevel 1 and then issuing the command "mount -no remount,ro /". This is not 100% reliable, occasionally this command will report a busy filesystem. As a workaround, I have modified the /etc/init.d/halt script so that it reports a failed unmounting and gives the user time to unmount the filesystem manually. The "Magic SysRq" keys can be used to accomplish this. I see this problem on two distinct machines. Neither of the too has any Raid, MD Array, LVM, etc... setting. Just one plain SATA/IDE disk in each case. The root filesystem is always a Reiserfs one. This is not a recent problem. I do not remember when it first occurred, but it persists for at least a year. Reproducible: Always Steps to Reproduce: 1. Reinstall the sysvinit package and initiate a reboot. Actual Results: The root filesystem is not unmounted properly on shutdown. Expected Results: On shutdown, all filesystems shut get unmounted. -- 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.