From: Andreas Dilger <adilger@sun.com>
To: Jan Kara <jack@suse.cz>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: Test script for 64KB blocksize
Date: Thu, 6 Dec 2007 11:35:22 -0700 [thread overview]
Message-ID: <20071206183522.GN3604@webber.adilger.int> (raw)
In-Reply-To: <20071206142120.GC6396@duck.suse.cz>
On Dec 06, 2007 15:21 +0100, Jan Kara wrote:
> attached is a test script which verifies that 64KB blocksize works in the
> modified code paths. It creates a filesystem with 64KB blocksize and
> excercises e2image, debugfs (and thus libext2fs) and e2fsck on it. You only
> need to modify paths to e2fsprogs in the first few lines of the script.
> Also if you don't apply a patch for 2-block lost+found from Andreas, you
> need to disable the first test which would fail otherwise.
This would be well suited to be added to e2fsprogs/tests with what looks
to be relatively few changes. That would ensure that it runs forever
in the future.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
prev parent reply other threads:[~2007-12-06 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 14:21 Test script for 64KB blocksize Jan Kara
2007-12-06 18:35 ` Andreas Dilger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071206183522.GN3604@webber.adilger.int \
--to=adilger@sun.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox