[Bug 521672] Re: Startup in Karmic with unclean filesystems leaves system in a wrong state
From the bug description, this sounds like an issue with the karmic mountall where it would continue when it shouldn't - this has been fixed in Lucid ** Changed in: mountall (Ubuntu) Status: New = Fix Released -- Startup in Karmic with unclean filesystems leaves system in a wrong state https://bugs.launchpad.net/bugs/521672 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
[Bug 521672] Re: Startup in Karmic with unclean filesystems leaves system in a wrong state
Is this behavior really by design? If so, it is a very bad one. By default, the system should wait until all file systems are available before letting the user log in. Otherwise, the user can suffer data loss as follows: 1) Boot with unmounted file systems. The mount points will look like empty directories. 2) The user logs in. 3) Program X starts up and finds that expected data Y is missing. 4) Program X proceeds to perform cleanup or initialization based on data Y having disappeared. Data loss has now already occurred in the case when program X writes to a different file system than where Y is located. For instance, if the home directory was mounted, but not the file system that contains my digital photos, a photo manager will now clear out metadata about the supposedly deleted pictures from its database. Some programs will ask the user first about this, but as is well known the user always answers yes. Otherwise: 5) The missing file system is mounted. 6) Program X keeps writing a clean slate of data in the location of Y, oblivious to the fact that it is now overwriting the real data, which has suddenly reappeared. -- Startup in Karmic with unclean filesystems leaves system in a wrong state https://bugs.launchpad.net/bugs/521672 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
[Bug 521672] Re: Startup in Karmic with unclean filesystems leaves system in a wrong state
If I drop to the shell I can let the fsck finish and start the X environment manually (just as a work around). If I don't do anything I can login via the GUI, but since my home directory is not ready by then I just get an empty desktop and a warning dialog like cannot access home directory, taking / as default. After which the session is pretty unusable of course, default installation is that most of the desktop is in the home directory. I also do not get an indication on the login screen that something is not ok (that something is still running in the background) -- Startup in Karmic with unclean filesystems leaves system in a wrong state https://bugs.launchpad.net/bugs/521672 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
[Bug 521672] Re: Startup in Karmic with unclean filesystems leaves system in a wrong state
Why is dropping to a shell a good solution? Doesn't the fsck eventually finish and then you can access your separate partition? It seems much better to give the user a fast boot and most of their desktop (sans corrupted home directory) than to just give them a shell with no home directory. ** Package changed: ubuntu = mountall (Ubuntu) -- Startup in Karmic with unclean filesystems leaves system in a wrong state https://bugs.launchpad.net/bugs/521672 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
