public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Rubin <mrubin@google.com>
To: Curt Wohlgemuth <curtw@google.com>
Cc: Theodore Tso <tytso@mit.edu>, Aioanei Rares <krnl.list@gmail.com>,
	Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	linux-ext4@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Mild filesystem corruption on ext4 (no journal)
Date: Mon, 8 Jun 2009 21:15:01 -0700	[thread overview]
Message-ID: <532480950906082115u77918911m2d44953014053c9b@mail.gmail.com> (raw)
In-Reply-To: <6601abe90906051442t294c2e79i3c6dc38c1d53e5e0@mail.gmail.com>

On Fri, Jun 5, 2009 at 2:42 PM, Curt Wohlgemuth<curtw@google.com> wrote:
> Just FYI: Frank Mayhar has recreated this issue in a recent kernel
> (though we're not seeing it with our 2.6.26 kernel + ext4 patches),
> and is actively working on it.

Sorry about this. We had a bunch of sick engineers in the last week or
so (including Frank). Hopefully he will be able to devote time to this
bug as he is getting back. We need it fixed for ourselves so we are
going to root cause it if no one beats us to it.

mrubin

      reply	other threads:[~2009-06-09  4:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 10:49 Mild filesystem corruption on ext4 (no journal) Alan Jenkins
2009-06-05 14:40 ` Aioanei Rares
2009-06-05 14:49   ` Alan Jenkins
2009-06-05 15:20     ` Eric Sandeen
2009-06-05 16:43       ` Alan Jenkins
2009-06-05 16:51         ` Kay Sievers
2009-06-05 21:42           ` Alan Jenkins
2009-06-06  4:17             ` Henrique de Moraes Holschuh
2009-06-05 18:12         ` Eric Sandeen
2009-06-05 21:32           ` Alan Jenkins
2009-06-05 22:02             ` Eric Sandeen
2009-06-05 18:01   ` Theodore Tso
2009-06-05 21:34     ` Alan Jenkins
2009-06-05 21:42     ` Curt Wohlgemuth
2009-06-09  4:15       ` Michael Rubin [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=532480950906082115u77918911m2d44953014053c9b@mail.gmail.com \
    --to=mrubin@google.com \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=curtw@google.com \
    --cc=krnl.list@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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