forced fsck while running on battery when mount count is exceeded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: upstart
Fsck will check an ext3 FS while on battery after x mounts (as specified in tune2fs), even if running on battery. Fsck has support for skipping such forced fsck runs, and indeed this was used properly under dapper with pure sysvinit. To laptop users this is really a critical bug. This bug has been reported many times, but unfortunately under the wrong package (sysvinit instead of upstart). I'm duplicating it here to try to get the attention of the right people, but ideally the old bug would be re-assigned to upstart. Losing 10 minutes of battery life to a "preventative" fsck is a real drag! I've personally encountered this on feisty/amd64 but there are reports of this being the case on edgy (probably x86) as well. The (mis-filed) bug report is here:
https:/