also sprach Theodore Ts'o <[email protected]> [2014-12-16 17:49 +0100]: > For newly created ext2/3/4 file systems, we no longer enable > periodic checking by default. Too many people complained, and > most file system authors assume that storage devices are perfect. > (The fact that they aren't is a different story, but that's the > cheap SSD/eMMC device's fault.)
I'll still employ those features. Better safe than sorry. And I would have never so much as dreamt about using the words "storage devices" and "perfect" in the same paragraph! ;) > Besides, what I recommend that the wise sysadmin set up these days is > this: > > https://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/tree/contrib/e2croncheck Both of these are good developments, but you cannot assume LVM on every machine. Especially embedded systems won't use them, and those will be particularly hurt by e2fsck running unexpectedly after a reboot. And while LVM is not priority:required, you won't be able to install the cronjob automatically anyway. All of this considered, and assuming it won't be hard, are there other reasons against a -q flag to e2fsck, which uses the same logic to print information to stdout or exit() as it uses to determine whether to run a long check? Cheers, -- .''`. martin f. krafft <[email protected]> @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems there is no place like ~
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
