On Wed, Aug 13, 2008 at 07:38:25PM -0000, ingo wrote:
> If said in my first post, that the file system was created by QNAP
> TS-209 NAS. It is an ext3 file system, but with some patches from
> QNAP applied (as far as I know to speed up RAID1).
Actually, it looks like it's an ext4 filesystem --- or at least, it's
ext3 with some pre-release version of ext4. The dumpe2fs program
shows that the extents feature is enabled, which is an ext4 feature.
dumpe2fs 1.40.8 (13-Mar-2008)
...
Filesystem features: has_journal filetype extents sparse_super
^^^^^^^
Given the lack of other features which are enabled, I'm guessing it's
an early pre-release version of ext4 --- and I'm wondering how early,
since we've fixed a lot of ext4 bugs lately. but thta's a problem for
the QNAP NAS folks, and hopefully they will be tracking the latest
kernels and taking the latest ext4 updates and bug fixes.
Be that as it may, it's surprising that e2sck is crashing here, given
that (a) dumpe2fs 1.40.8 was able to display the filesystem feature
set, and (b) the code in e2fsck does substantially the same thing, and
that hasn't changed much between 1.40.8 and 1.41.0.
In any case, given the extents feature, you are not going to be able
to mount it using a stock Ubuntu kernel, since last I checked it
doesn't enable ext4 by default. It may be that an Ubuntu Interpid
kernel has the correct support, but you'll probably need to do the
following before it will mount.
1) Install e2fsprogs 1.41.0
2) Run "tune2fs -E test_fs /dev/sdc3"
3) Mount it via "mount -t ext4dev /dev/sdc3 /mnt"
OK, so let's review the bidding here.
> filesystem is corrupted
> cannot be mounted
Not necessarily; this is an ext4 filesystem, so unless you have the
ext4 filesystem compiled into your kernel, (and given Ubuntu's
unfortunate choice of vol_id instead of blkid libraries, you have to
explicitly tell mount to use the ext4 module via "mount -t ext4dev" ),
it's not mountable as an ext3 filesystem.
> Hardy: e2fsck crashes
That's wierd. I think we'll need to run it under a debugger and see
if we can get a useful stack trace out of it. Possibly we'll need to
do this using an unstripped binary or a recompiled-from-scratch
binary.
With the latest Lenny packages e2fsprogs now has debug packages, but
unfortunately not the version that Ubuntu Hardy is shipping with.
> OpenSUSE e2fsck reports message and exits
That's also wierd. I'm not sure what's going on there.
> Lenny reports the faulty things, is able to correct some, but not all.
You haven't uploaded what Lenny's e2fsck has reported, so I can't
really evaluate it. That also might be because whatever QNAS has
cooked up is non-standard and an older pre-release version of ext4,
and Lenny is shipping with e2fsprogs 1.41.0, which is designed to work
with the latest version of ext4 as can be found in the
mainline kernels.
I hope this is helpful,
- 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
