[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 15 Feb 2011 12:29:22 -0500
From: Ted Ts'o <tytso@....edu>
To: Dave Chinner <david@...morbit.com>
Cc: Amir Goldstein <amir73il@...il.com>, Jan Kara <jack@...e.cz>,
Michael Rubin <mrubin@...gle.com>,
Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [LSF/MM TOPIC] Drop ext2/ext3 codebase? When?
On Tue, Feb 15, 2011 at 03:28:37PM +1100, Dave Chinner wrote:
>
> What scripts are needed? xfstests has the $MKFS_OPTIONS and
> $MOUNT_OPTIONS environment variables for customising your mkfs and
> mount parameters for each test run, so isn't testing ext3
> filesystems with the ext4 code should just be a matter of setting
> these appropriately?
Correct, this doesn't require changes to xfstests.
What is needed for this ext4/ext3-using-ext4 testing is a wrapper
script *around* xfstests that sets up the enviornment variables
correctly, and uses different devices for the "common case"
combinations of mkfs and mount options (where we would keep an aged
file system around), and for those devices which we don't think are
valuable enough to dedicate a reserved file system image, we'd have to
mkfs a special version of that filesystem for TEST_DEV.
(I'm not sure why xfstests doesn't use freshly created file in the
case where SCRATCH_DEV is defined by TEST_DEV is not, but it doesn't;
as far as I know there are no tests where it uses both TEST_DEV and
SCRATCH_DEV, is there?)
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists