On Thu, Mar 13, 2008 at 10:22:25PM +0100, Christian Kujau wrote: > On Thu, 13 Mar 2008, Theodore Tso wrote: >>> http://nerdbynature.de/bits/e2fsprogs.pu/md4.log >>> http://nerdbynature.de/bits/e2fsprogs.pu/ >> >> Hmm. What I really need is *first* e2fsck run, to see what it did. > > The md4.log is the first e2fsck run: > > 1) mounted fs, noticed error message in dmesg > 2) umounted fs > 3) ran e2fsck, right on top of this md4.log file... > > The 2nd run is the one after the "/dev/md4: clean" message in md4.log Oh, right. Sorry, I missed that. I think I know what's going on. The problem is we're not supporting long symlinks which are in extents format. That's something which we changed, but we're going to change back (since we need it to support filesystems with > 2**32 blocks). I'll make e2fsprogs flexible enough to support both forms of long symlinks. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
