Your message dated Wed, 18 Jun 2008 20:23:11 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: e2fsprogs: Make scheduled fscks more user-friendly
has caused the Debian Bug report #486261,
regarding e2fsprogs: Make scheduled fscks more user-friendly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
486261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486261
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: e2fsprogs
Version: 1.40.8-2
Severity: wishlist
*** Please type your report below this line ***
This is related to another feature request I just made against sysvinit.
I'll follow up with it's bug number when the BTS replies to my mail.
Also, I've discussed it in this thread:
http://lists.debian.org/debian-user/2008/06/msg00833.html
Here are my e2fsprogs-specific feature requests. Let me know if I should
file them against other packages instead:
1) Let users cleanly interrupt fsck
If users hit ctrl+c (or maybe ESC), fsck should guarantee that the
filesystem is in a relatively safe state before terminating.
fsck probably does do this already, but some users on the threads
weren't sure, and thought that hitting ctrl+C might be an unsafe
operation.
2) Allow 'info gathering' fsck mode, while partition is mounted r/w.
2.1) Let fsck (or some related utility) scan for errors while the
partitions are mounted read/write. This will probably find a lot of
bogus errors. This can be run in the background by the desktop
environment, while the user is logged in.
2.2) Let fsck be run against that gathered info, so it can quickly check
which errors are real, and which ones need to actually be fixed. If the
info was gathered recently, and is complete, fsck should be able to
safely record that the drive was scanned (pushing back the time of the
next scheduled fsck for the partition).
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=en_ZA.utf8, LC_CTYPE=en_ZA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages e2fsprogs depends on:
ii e2fslibs 1.40.8-2 ext2 filesystem libraries
ii libblkid1 1.40.8-2 block device id library
ii libc6 2.7-11 GNU C Library: Shared libraries
ii libcomerr2 1.40.8-2 common error description library
ii libss2 1.40.8-2 command-line interface parsing lib
ii libuuid1 1.40.8-2 universally unique id library
e2fsprogs recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Your choices are:
1) Don't reboot so much (use suspend instead)
2) Interrupt the fsck using ^C by setting e2fsck.conf as I described
3) Disable the periodic check using tune2fs --- we're just more paranoid
than SGI's XFS, which is optimized for data center quality RAID arrays,
and not crappy PC disks which tend to fail and/or corrupt data much more
frequently --- but if you don't want to do the periodic checks, you can
disable them.
In any case, there's nothing that I plan to change with e2fsprogs.
- Ted
--- End Message ---
