[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <20090501105757.GD3209@webber.adilger.int>
Date: Fri, 01 May 2009 04:57:58 -0600
From: Andreas Dilger <adilger@....com>
To: Nick Dokos <nicholas.dokos@...com>
Cc: linux-ext4@...r.kernel.org, "Theodore Ts'o" <tytso@....edu>,
Valerie Aurora <vaurora@...hat.com>
Subject: Re: [PATCH 0/6][64-bit] Overview
On May 01, 2009 04:46 -0400, Nick Dokos wrote:
> With this set of patches, I can go through a mkfs/fsck cycle with a
> 32TiB filesystem in four different configurations:
>
> o flex_bg off, no raid parameters
> o flex_bg off, raid parameters
> o flex_bg on, no raid parameters
> o flex_bg on, raid parameters
Nick,
sorry to be so slow getting back to you. Attached are the relatively
simple test programs we use to verify whether large block devices and
large filesystems are suffering from block address aliasing.
The first tool (llverdev) will write either partial or fill data patterns
to the disk, then read them back and verify the data is still correct.
The second tool (llverfs) will try to allocate directories spread across
the filesystem (if possible, using EXT2_TOPDIR_FL) and then fill the
filesystem partially or fully with a data pattern in ~1GB files and
then read them back for verification.
This isn't really a stress test, but rather just a sanity check for
variable overflows at different levels of the IO stack.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
View attachment "llverdev.c" of type "text/plain" (15348 bytes)
View attachment "llverfs.c" of type "text/plain" (18574 bytes)
Powered by blists - more mailing lists