[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200805191439.36577.chris.mason@oracle.com>
Date: Mon, 19 May 2008 14:39:36 -0400
From: Chris Mason <chris.mason@...cle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Eric Sandeen <sandeen@...hat.com>, Theodore Tso <tytso@....edu>,
Andi Kleen <andi@...stfloor.org>, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes
On Monday 19 May 2008, Chris Mason wrote:
>
> Here's a test workload that corrupts ext3 50% of the time on power fail
> testing for me. The machine in this test is my poor dell desktop (3ghz,
> dual core, 2GB of ram), and the power controller is me walking over and
> ripping the plug out the back.
Here's a new version that still gets about corruptions 50% of the time, but
does it with fewer files by using longer file names (240 chars instead of 160
chars).
I tested this one with a larger FS (40GB instead of 2GB) and larger log (128MB
instead of 32MB). barrier-test -s 32 -p 1500 was still able to get a 50%
corruption rate on the larger FS.
-chris
Download attachment "barrier-test" of type "application/x-python" (6070 bytes)
Powered by blists - more mailing lists