On Wed, Aug 13, 2008 at 09:21:20PM -0000, ingo wrote:
> Many thanks Ted,
>
> So I now know where to go and I discard the unusable partitition. But I
> will get my NAS back and repaired soon (I hope) and then be able to
> create a 'virgin QNAP ext3' and check with Lenny or even Intrepid
> whether it is a ext4-alpha!
It is definitely doing something non-standard with the extents
(assuming that this wasn't a corrupted filesystem). See this:
Durchgang 1: Prüfe Inodes, Blocks, und Größen
Inode 26247171 has an ungültig extent
(logical Block 0, ungültig physical Block 43980517704194, len 478256)
Bereinige? nein
At a guess, it's not zeroing out the high bits of the extents
structure when we extended the original Lustre extent patches to
support > 32-bit block numbers. The length looks very wrong as well.
So this is either a corrupted extent tree or an corrupted inode, or
your QNAP nas is using a very old set of ext4 extents patches.
> So for the moment, dont't worry about the ext4 story, just fsck.ext3
> should not crash when operating on such a 'homebrew ext4'.
Yep, agreed.
Can you do me a favor? Can you create a very small partition (say, 64
megabytes) on the NAS system, then pull the drive, and zero the
partition out (using dd if=/dev/zero...) then put the drive back, have
the NAS install its ersatz ext3-with-extents/early-ext4 filesystem on
it, place 2 or 3 files ranging in size from 1k to 128k, and then pull
the drive, compress the image, and send it to me? It would be very
useful for trying to figure out exactly what they are doing, and would
help reproducing the bug.
If that's too much trouble, you can just send me the results of "dd
if=/dev/sdc3 of=out.img bs=4k count=200"? That will be enough for
dumpe2fs to work, and hopefully enough for me to try reproducing the
e2fsck crash.
- Ted
--
e2fsck crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/257048
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
