-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bob McGowan wrote: > This brings up the question, though, as to why these forced checks are > done in the first place. The man page talks about failed hardware and > kernel bugs, etc., but ...
Very interesting point. Indeed running fsck when the shutdown was clean seems pointless. Many people or manuals warn you in big letters not to disable them, but then again don't provide info about what parameters are good. > A server may stay up and running for months, perhaps longer (?), whereas > personal system may be shut down every day. So counts are quickly > reached in the personal system case, while time limits are probably not > only exceeded in the server case, they may be exceeded by substantial > amounts of time. Exactly. Thus a server (where it counts) is never checked for months, and a PC (where it doesn't matter so much) is pestered with fsck all the time, usually while the user needs the PC in a hurry. > Which means I need to periodically run fsck manually, to be sure things > are OK, but at least it's under my control. Good idea. Run it when it's not in the way. My $.02: If it was all that important, there would be an option to run fsck at shut down instead of startup. And clearly whoever started fsck had no idea that it would take longer and longer as drives got newer. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkuZP/cACgkQ+VSRxYk4408wpwCgrwGdCbKaCmY3RR3fVVY1hLWD z4EAnA0UDs/CyApcDZjf7gryV/lugfcl =7VwO -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b993ff7.1010...@web.de
