fsck should be disabled for laptops running on battery power

Bug #116289 reported by Patrick
8
Affects Status Importance Assigned to Milestone
e2fsprogs (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Every X times (usually 30 times) you boot up ubuntu from a hard drive, that hard drive will be checked for errors (fcheck). This is of course perfectly fine!
This also occurs on laptops running on batteries. I was wondering if it is possible to detect whether a laptop is running on batteries that early in the boot process. If that is possible if the hdd check can be done the first time the computer boots while not being at battery power, after the X^th time that the computer has booted at all (I hope this made it a bit clear).

description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in recently. We were wondering if this is still an issue for you? Thanks in advance.

Revision history for this message
Patrick (hanckmann-gmail) wrote :

It is still an issue.

Revision history for this message
Brian Murray (brian-murray) wrote :

I've personally noticed the cryptmount is aware of when your system is on battery and does not perform an fsck in this situation.

Revision history for this message
David Douard (david-douard) wrote :

Hi, I have the same requirement. I boot my laptop almost every day in the train (since I cannot hibernate it anymore, but that's another story...), I regularly "fall" on the fsck'ed boot.

I would really appreciate Ubuntu be clever enough not to do such tasks when on battery.

Revision history for this message
Theodore Ts'o (tytso) wrote :

E2fsprogs already has this support for years. This is a bug in Ubuntu's kernel, or modules. The problem the acpi ac_adapter module is compiled as a module instead of being built-into the kernel, and it isn't getting loaded before the filesystem fsck is run.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.