Package: e2fsprogs
Version: 1.37-2
Severity: normal
File: /sbin/fsck.ext3
I'm not sure fsck is supposed to sync afterward (but I assume it does).
But in any case it doesn't sync after checking a fs via a loopback.
It's a 500GB encrypted partition. I ran fsck.ext3 with -D (there were no
errors, but there was a nice progress bar while it rebuilt a directory).
After finishing it sat for quite a while writing data before exiting,
but running sync right afterward took even longer then that, so it must
have had quite a bit of data to write. (If I don't sync manually, then
losetup -d does it, and takes a while.)
(This happens every time I do this, I just remembered to report it now.
It's not because it was syncing other data - the computer was idle.)
-Ariel
PS. It's quite possible that it's the loopback that has the bug, and
doesn't sync when told to, but I feel that fsck should probably work
around it (if that's indeed the case).
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.9
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages e2fsprogs depends on:
ii e2fslibs 1.37-2 ext2 filesystem libraries
ii libblkid1 1.37-2 block device id library
ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an
ii libcomerr2 1.37-2 common error description library
ii libss2 1.37-2 command-line interface parsing lib
ii libuuid1 1.37-2 universally unique id library
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
