On Sun, Oct 15, 2006 at 10:27:20PM -0400, Jason Spiro wrote:
> Package: e2fsprogs
> Version: 1.39-1
> Severity: wishlist
>
> Debian GNU/Linux is sometimes frustrating and makes me want to go back
> to using Windows. One example of this is when I am due for a
> filesystem check. Windows gives me 10 seconds in which I can press any
> key to cancel the check. If I don't press a key, then it starts the
> check. But Linux takes away my control of my own computer. It runs the
> check whether I want it to or not.
>
> It would be great if I was warned 10 seconds before a boot-time check
> ran, just like in Windows, and could postpone the check until next
> boot. Remember, it's my PC, not yours. :-)
See man e2fsck.conf(5). Create a file /etc/e2fsck.conf, with the
contents:
[options]
allow_cancellation = true
Then you should be able to type ^C while it is doing a check, and
cancel the fsck. (It is safe to abort fsck while it is scanning the
filesystem.)
Note that if you don't like the frequency at which the filesystem is
being checked, you can adjust this using tune2fs. If you want the
Mcirosoft-default behaviour of "fat, dumb, and happy", where no checks
are done, until the filesystem is so obviously corrupted that the
system crashes, you can get bug-for-bug Microsoft compatibility in
this respect by using the command:
tune2fs -c 0 /dev/hdXXX
But to quote from the tune2fs man page:
You should strongly consider the consequences of disabling mount-
count-dependent checking entirely. Bad disk drives, cables,
memory, and kernel bugs could all corrupt a filesystem without
marking the filesystem dirty or in error. If you are using
journaling on your filesystem, your filesystem will never be marked
dirty, so it will not normally be checked. A filesystem error
detected by the kernel will still force an fsck on the next reboot,
but it may already be too late to prevent data loss at that point.
Regards,
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
