linux-ext4 - Re: ext4 corruption on 17TB file system during power cycle test

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 13 Jun 2012 09:42:34 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Ming Lei <Ming.Lei@...erbed.com>
CC:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: ext4 corruption on 17TB file system during power cycle test

On 6/13/12 9:30 AM, Ming Lei wrote:
> We actually ran into problem in our real power cycle testing. We used
> fsck -p option and then mount the ext4 file system but during test
> after the power cycle, kernel found EXT4 error and then force ext4
> mount become read only. Do you think the problem is inside kernel?

Hm you said:

> After the box came up, I ran fsck -f to check inconsistency.

But you you say:

> We used fsck -p option an then mount the ext4 filesystem

so which was it?

I'm not clear on the steps you took in this test.

But it's quite possible that userspace log replay left errors that the kernel later discovered.

Again, I'll suggest retesting with e2fprogs-1.42.4, and preferably an upstream kernel.  If you still have problems, we can investigate further.  If it's only present on your distro versions, you can file a bug w/ the distro.

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html