linux-kernel - Re: corrupted ext4 1000gb filesystem (2.6.32, debian stable)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPweEDxE=O7=uBPp2EMbdJ7LZ2afnB773hDsYk7R45ZOOZeVRA@mail.gmail.com>
Date:	Tue, 2 Aug 2011 15:54:25 +0100
From:	Luke Kenneth Casson Leighton <luke.leighton@...il.com>
To:	"Ted Ts'o" <tytso@....edu>,
	Luke Kenneth Casson Leighton <luke.leighton@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: corrupted ext4 1000gb filesystem (2.6.32, debian stable)

On Tue, Aug 2, 2011 at 3:27 PM, Ted Ts'o <tytso@....edu> wrote:

> *However*, if you have a RAID1 setup where the data on the disks are
> consistent, this can be the cause of much mischief.  Depending on
> which disk you read from the mirror, you might get different results.
> Once that's the case, all bets with e2fsck are off.

 ok - that would explain why the problem has appeared to go away when
i reduced the RAID1 to a single drive.  i'm presently waiting for the
two 1.5Tb drives to sync up (estimated another 24 hrs)

> Finally, I strongly recommend that when you are doing this kind of
> repair work, that you save a copy of everything you do useing a
> program like "script".  A transcript of the e2fsck output can be
> critally useful.  Reviewing the transcript can also be useful in
> identifying mistakes that you might have made during the recovery
> process.

 ok i'll bear that in mind.

> Regards,
>
>                                                - Ted
>
> P.S.  Note that if you are running e2fsck, and you haven't mounted
> the disk yet, if you are seeing failures after a second run of e2fsck,
> then it obviously can be a failing in the ext4 kernel code.

 ok, thank you ted.  based on that, i'll keep doing reports (and make
sure i use typescript).

 l.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/