From: Andreas Dilger <adilger@clusterfs.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Kalpak Shah <kalpak@clusterfs.com>,
linux-ext4 <linux-ext4@vger.kernel.org>,
TheodoreTso <tytso@mit.edu>
Subject: Re: Random corruption test for e2fsck
Date: Thu, 12 Jul 2007 16:16:24 -0600 [thread overview]
Message-ID: <20070712221624.GA5880@schatzie.adilger.int> (raw)
In-Reply-To: <20070712110923.GA500@one.firstfloor.org>
On Jul 12, 2007 13:09 +0200, Andi Kleen wrote:
> > "dd if=/dev/urandom bs=1k ..." than to spin in a loop getting 16-bit
> > random numbers from bash. We would also be at the mercy of the shell
> > being identical on the user and debugger's systems.
>
> With /dev/urandom you have the guarantee you'll never ever reproduce
> it again.
That is kind of the point of this testing - getting new test images for
each user that runs "make check" or "make rpm". I'm We also save the
generated image before e2fsck touches it so that it can be used for
debugging if needed.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2007-07-12 22:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 13:07 Random corruption test for e2fsck Kalpak Shah
2007-07-10 14:58 ` Theodore Tso
2007-07-10 15:42 ` Eric Sandeen
2007-07-11 7:03 ` Kalpak Shah
[not found] ` <20070711094410.GM6417@schatzie.adilger.int>
2007-07-11 17:43 ` Theodore Tso
2007-07-12 5:15 ` Andreas Dilger
2007-07-12 5:52 ` Andreas Dilger
2007-07-10 15:47 ` Eric Sandeen
2007-07-11 16:03 ` Andreas Dilger
2007-07-11 15:20 ` Andi Kleen
2007-07-12 5:19 ` Andreas Dilger
2007-07-12 11:09 ` Andi Kleen
2007-07-12 22:16 ` Andreas Dilger [this message]
2007-07-12 22:24 ` Andi Kleen
2007-07-13 7:12 ` Kalpak Shah
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=20070712221624.GA5880@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=andi@firstfloor.org \
--cc=kalpak@clusterfs.com \
--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;
as well as URLs for NNTP newsgroup(s).