You are not logged in.
Previously, Arch used to skip fscking on boot when it was on battery. I mean the fscks that are done every x mounts. Now these periodic fscks run whether or not my netbook is on battery. (My /boot is ext2; / and /home are ext4.)
Is this a bug or a feature? Is it better for Arch to proceed with a fsck if there is a risk of the battery running out or to defer a fsck even if there may be filesystem issues?
Is there a way to configure this behaviour? Some of my research suggests this can be set in /etc/e2fsck.conf, but this file does not exist on my system, and I'm not sure if it's applicable to ext4.
Offline
from "man e2fsck";
e2fsck is used to check the ext2/ext3/ext4 family of file systems.
and there is a manpage for configuring e2fsck.conf as well. Becuase a *.conf isn't created only means its running in default behavior.
Offline
Wow, I just skipped right over the first sentence of that man page. I suck at teh Linux. Sorry. :-/
I did see the man page for e2fsck.conf, but missed that I can create it myself if it doesn't exist.
I would still like advice on whether or not it's better to defer fsck on battery. I haven't found much on the forums re: this, and my google-fu results seem inconclusive. Apologies in advance if I am missing something (else) obvious.
Offline
I have it set to fsck every 20 mounts -- and deferred when on battery. If I see that a check was deferred I know to plug in for the next boot (or two...).
Offline
I read that as 'every 20 minutes' and was like 8-0.
But then I was like, oooooooooooooooooh: ^minutes^mounts^
(Sorry, it's early here... :-)
Thanks!
Offline
Hi,
it looks like e2fsck uses the old /proc/acpi interface which is no longer present in Arch:
http://git.kernel.org/?p=fs/ext2/e2fspr … =HEAD#l247
That interface has been marked as “deprecated” in Linux 2.6.39.
Offline