On 12/19/06, Andrew Morton <[email protected]> wrote:
Wow. I didn't expect that, because Mark Haber reported that ext3's data=writeback fixed it. Maybe he didn't run it for long enough?
I don't think it did fix it for Mark: http://marc.theaimsgroup.com/?l=linux-kernel&m=116625777306843&w=2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: 2.6.19 file content corruption on ext3
- From: Andrei Popa <[email protected]>
- Re: 2.6.19 file content corruption on ext3
- From: Andrei Popa <[email protected]>
- Re: 2.6.19 file content corruption on ext3
- From: Linus Torvalds <[email protected]>
- Re: 2.6.19 file content corruption on ext3
- From: Andrei Popa <[email protected]>
- Re: 2.6.19 file content corruption on ext3
- From: Linus Torvalds <[email protected]>
- Re: 2.6.19 file content corruption on ext3
- From: Andrew Morton <[email protected]>
- Re: 2.6.19 file content corruption on ext3
- From: Andrei Popa <[email protected]>
- Re: 2.6.19 file content corruption on ext3
- From: Andrew Morton <[email protected]>
- Re: 2.6.19 file content corruption on ext3
- From: Andrei Popa <[email protected]>
- Re: 2.6.19 file content corruption on ext3
- From: Andrew Morton <[email protected]>
- Re: 2.6.19 file content corruption on ext3
- Prev by Date: Re: GPL only modules
- Next by Date: [PATCH] scsi_execute_async() should add to the tail of the queue
- Previous by thread: Re: 2.6.19 file content corruption on ext3
- Next by thread: Re: 2.6.19 file content corruption on ext3
- Index(es):
 |