linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Ming Lei <Ming.Lei@riverbed.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: ext4 corruption on 17TB file system during power cycle test
Date: Wed, 13 Jun 2012 09:42:34 -0500	[thread overview]
Message-ID: <4FD8A6DA.90404@redhat.com> (raw)
In-Reply-To: <2CE44BD3DBCF9541909CCB42F11CA392828B4D@SFO1EXC-MBXP06.nbttech.com>

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

      reply	other threads:[~2012-06-13 14:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 13:49 ext4 corruption on 17TB file system during power cycle test Ming Lei
2012-06-13 14:10 ` Eric Sandeen
2012-06-13 14:17   ` Ming Lei
2012-06-13 15:44     ` Ted Ts'o
2012-06-13 14:20   ` Ming Lei
2012-06-13 14:30   ` Ming Lei
2012-06-13 14:42     ` Eric Sandeen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FD8A6DA.90404@redhat.com \
    --to=sandeen@redhat.com \
    --cc=Ming.Lei@riverbed.com \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).