On Mon, Jul 17, 2006 at 07:12:00PM +0200, Zoran Dzelajlija wrote:
> But, bzip2 is used like
>
> bzip2 -d foo.tar.bz2
> tar xfS foo.tar
>
> ... and foo.tar is only 500MB, not 200GB. Compare, if you wish:
Hmm, last time I checked bzip2 -d didn't create sparse files when
decompressing (that's why I wrote make-sparse). But even if it did,
it's surprising that tar xvfS would be any better because it still
needs to read all of the zeros since we don't have the Solaris
interface to find the size of "holes" in sparse files so we can skip
over to the non-zero blocks. But anyway, it's something for me to
look at.
> Anyway, back to the bug report: running e2fsck without -n fixes the htrees
> for two directories, and a repeated e2fsck finds no errors. Accessing the
> directory which would previously make kernel oops now works too.
OK, that's useful. Did you keep the e2image from before you fixed it
viua e2fsck without -n. At this point, the e2image file or just the
files created by:
debugfs /dev/sdb1
debugfs: dump <1060239> /tmp/1060239.dir
debugfs: dump <1630724> /tmp/1630724.dir
debugfs: quit
.... would be very helpful.
Thanks,
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
