On Tue, Aug 2, 2011 at 1:54 AM, Ben Hutchings <[email protected]> wrote: > On Tue, 2011-08-02 at 01:29 +0100, lkcl wrote: >> Package: linux-2.6 >> Version: 2.6.32-5 > > Not an actual version number. > >> Severity: important >> >> >> running 2.6.32-5-amd64, after running fsck on a corrupted ext4 >> filesystem which is an LVM partition on top of a RAID1 mirror with 3 >> drives and is 1tb in size, there are *still* errors after the fsck, >> as detected by running fsck a 2nd time. > > That would be a bug in e2fsck, not the kernel. But I would be more > inclined to suspect some sort of hardware problem.
... across three drives?? all three physical drives have a hardware problem? yes i know they're WD 1.5Tb external USB2 drives, but even so. >> i'd say this is fairly serious, and am not going to hang about: will >> be moving this data onto ext3 as quickly as possible. > > And yet ext4 works fine for other people. yehh... are they using 1Tb logical volumes on triple-RAID1'd 1.5Tb drives, though - that's the question. l. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/capweedykmwyb0s3pp5vcd91tb1-m10hn8n58kbkujysfrcp...@mail.gmail.com
