Re: Mild filesystem corruption on ext4 (no journal)
- From: Michael Rubin <mrubin@xxxxxxxxxx>
- Date: Mon, 8 Jun 2009 21:15:01 -0700
On Fri, Jun 5, 2009 at 2:42 PM, Curt Wohlgemuth<curtw@xxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Mild filesystem corruption on ext4 (no journal)
- From: Alan Jenkins
- Re: Mild filesystem corruption on ext4 (no journal)
- From: Aioanei Rares
- Re: Mild filesystem corruption on ext4 (no journal)
- From: Theodore Tso
- Re: Mild filesystem corruption on ext4 (no journal)
- From: Curt Wohlgemuth
- Mild filesystem corruption on ext4 (no journal)
- Prev by Date: Re: /proc/kcore has a unreasonable size(281474974617600) in x86_64 2.6.30-rc8.
- Next by Date: Re: linux-next: ext4 tree build warning
- Previous by thread: Re: Mild filesystem corruption on ext4 (no journal)
- Next by thread: Can kmalloc( ) with __GFP_WAIT flag fail?
- Index(es):
Relevant Pages
|
Loading