This bug is not actually a duplicate of #219382. #219382 is a generic bug about filesystem checks on boot based on on_ac_power. This bug is about behavior in relation to JFS which should be handled separately.
If a JFS FS is ever unmounted unclearly, the filesystem needs to be checked. If the FS is mounted without a fsck, the FS will be read only. The effect is that if an install with a JFS root FS ever crashes, looses power, or otherwise shuts down uncleanly and the system is then booted up without AC power, the system will silently and without warning mount the root FS read only and fail to start a variety of applications, most notably GDM. If a user does not know how to fsck their root by hand, the system will become unusable until the system is booted with AC power present. A fsck on JFS takes well under a minute to run so concerns about battery power are less important than they might be in ext3. I see no reason to have the checkroot.sh script always run the fsck if the system is JFS. This will address fix this issue for JFS laptop users. I've included a patch that does this. It may not be the right place (I don't know the codebase well) but it fixes the issue and should explain roughly what needs to happen ** Attachment added: "checkroot.sh.diff" http://launchpadlibrarian.net/30436598/checkroot.sh.diff ** Package changed: ubuntu => sysvinit (Ubuntu) ** Changed in: sysvinit (Ubuntu) Status: New => Confirmed ** This bug is no longer a duplicate of bug 219382 fsck not run on boot if on battery power ** Summary changed: - Jaunty: jfs filesystem being mounted read-only + JFS root FS mounted read-only on battery power after unclean umount ** Description changed: - Today, for the second time, when booting my computer (a Dell Laptop), - mounted my filesystem as readonly (jfs for the matters). + If a JFS FS is ever unmounted unclearly, the filesystem needs to be + checked. If the FS is mounted without a fsck, the FS will be read only. + The effect is that if an install with a JFS root FS ever crashes, looses + power, or otherwise shuts down uncleanly and the system is then booted + up without AC power, the system will silently and without warning mount + the root FS read only and fail to start a variety of applications, most + notably GDM. If a user does not know how to fsck their root by hand, the + system will become unusable until the system is booted with AC power + present. - The first time this happened was during aprils fool, when I couldn't get - it to mount the filesystem correctly for some time (rebooted the system - 5 or 6 times before it actually mounted it as r/w). + A fsck on JFS takes well under a minute to run so concerns about battery + power are less important than they might be in ext3. I see no reason to + have the checkroot.sh script always run the fsck if the system is JFS. + This will address fix this issue for JFS laptop users. - Today it happened again. - The only thing in common that i see is that, both times i was running on batteries. And when connected the power the problem got away. I can't see to find ways to reproduce it. - - But I think it might be related to the fact the fsck is not ran if the - system is on batteries. So, it might be that the fs gets corrupted by - some reason, and on reboot its not clean, and hence mount can't remount - it r/w (thou I haven't seen any message indicating this). - - If any additional info needed please tell me. + To reproduce the bug: (1) unmount JFS root FS uncleanly; (2) boot system + without AC power. -- JFS root FS mounted read-only on battery power after unclean umount https://bugs.launchpad.net/bugs/361023 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
