Automatic fsck leaves partition inaccessible without any notification.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: e2fsprogs
I don't know if this is the correct package to file this bug against, but here it is:
In karmic, when an automatic fsck is started on a non-system partition during boot, the system continues the boot process as it should while the fsck is run in the background. This is an improvement over the earlier behaviour (that the entire boot process was paused while waiting for fsck to finish).
My problem is that as the fsck process continues for several minutes after the boot has finished, the partition remains unmounted (and unmountable) without any notification to the user why this happens. The only way to know what's going on is to specifically check in the system monitor, top, ps, etc. if e2fsck is running.
Once the fsck is done, the partition gets mounted automatically as it should, so that's not the problem.
Shouldn't the user be notified why the partition is inaccessible?
Is it possible to get a notification (after login) saying something like:
"A file system integrity check on the device /dev/sdb2 is running in the background. The disk will be accessible when this is ready"
Even better if there would also be a progress bar or an estimated time plus the option to cancel it (and reschedule it to the next boot).
lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10
apt-cache policy e2fsprogs
e2fsprogs:
Installerad: 1.41.9-1ubuntu1
Kandidat: 1.41.9-1ubuntu1
Versionstabell:
*** 1.41.9-1ubuntu1 0
500 http://
100 /var/lib/
affects: | ubuntu → e2fsprogs (Ubuntu) |
affects: | e2fsprogs (Ubuntu) → ubuntu |
Probably, but this is not an e2fsprogs issue