From: Pat LaVarre <p.lavarre@ieee.org>
To: rddunlap@osdl.org
Cc: zachary@cse.ucsc.edu, linux-fsdevel@vger.kernel.org
Subject: Re: fs test suite
Date: 07 Oct 2003 12:54:57 -0600 [thread overview]
Message-ID: <1065552897.8172.28.camel@patehci2> (raw)
In-Reply-To: <20031007101602.658d6638.rddunlap@osdl.org>
> Are you looking for a test (suite) that tests
> fs metadata moreso than fs IO? People have
> asked for that a few times, but I don't know
> of one that is made for that.
May I ask you to elaborate? I'm not yet confident I understand the
question. I mean to ask how do I increase my confidence that 2.4.x and
2.6.x udf.ko will read back to me what I wrote thru it. I figure that
mixes together metadata and data, since the metadata tells me how much
and from where I read back my data.
I see my semi-private linux_udf@hpesjro.fc.hp.com thread titled "zeroes
read back more often than appended" says a write-read-compare test as
trivial as fopen-fwrite-fclose doesn't yet work.
I blame that either on my own bonehead newbie errors i.e. illegit test
setup, else low-hanging bugs. I'm hear wondering, can I easily look for
other low-hanging fruit.
> http...
Thank you! I will pursue:
http://www.codemonkey.org.uk/cruft/
http://www.zip.com.au/~akpm/linux/patches/stuff/
http://ltp.sourceforge.net/
http://www.iozone.org
http://www.google.com/search?q=postmark+linux
http://www.connectathon.org/
http://www.google.com/search?q=bonnie+linux
Pat LaVarre
next prev parent reply other threads:[~2003-10-07 18:55 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 4:11 fs test suite Pat LaVarre
2003-10-07 14:17 ` Randy.Dunlap
2003-10-07 14:59 ` Zachary Peterson
2003-10-07 17:16 ` Randy.Dunlap
2003-10-07 18:54 ` Pat LaVarre [this message]
2003-10-07 18:58 ` Randy.Dunlap
2003-10-07 19:26 ` Pat LaVarre
2003-10-20 9:12 ` srfs - a new file system Nir Tzachar
2003-10-20 21:00 ` Eric Sandall
2003-10-21 12:07 ` Nir Tzachar
2003-10-21 14:29 ` Brian Beattie
2003-10-21 16:59 ` Jan Harkes
2003-10-23 13:58 ` Pavel Machek
2003-10-24 9:28 ` Nir Tzachar
2003-10-22 4:57 ` Erik Andersen
2003-10-22 10:16 ` Nir Tzachar
2003-10-22 14:22 ` Jan Harkes
2003-10-23 7:50 ` Nir Tzachar
2003-10-23 12:33 ` Jan Hudec
2003-10-23 20:12 ` Pat LaVarre
2003-10-24 9:21 ` Nir Tzachar
2003-10-24 12:08 ` Matthew Wilcox
2003-10-24 19:14 ` Nir Tzachar
2003-10-24 14:38 ` Jan Harkes
2003-10-24 19:16 ` Nir Tzachar
2003-10-24 20:11 ` Andreas Dilger
2003-10-24 20:24 ` Pat LaVarre
2003-10-24 20:38 ` Andreas Dilger
2003-10-24 20:52 ` Pat LaVarre
2003-10-24 21:00 ` Nir Tzachar
2003-10-24 21:22 ` Pat LaVarre
2003-10-24 23:03 ` Nir Tzachar
2003-10-25 0:23 ` Bryan Henderson
2003-10-25 10:37 ` Nir Tzachar
2003-10-24 21:15 ` Andreas Dilger
2003-10-24 20:53 ` Nir Tzachar
2003-10-25 8:01 ` Jan Hudec
2003-10-22 10:21 ` Nir Tzachar
2003-10-25 9:27 ` Implementing writepage Charles Manning
2003-10-25 16:18 ` David Woodhouse
2003-10-25 22:40 ` Charles Manning
2003-10-26 10:25 ` David Woodhouse
2003-10-26 15:28 ` Matthew Wilcox
2003-10-26 18:47 ` Mark B
2003-10-26 20:40 ` Charles Manning
2003-10-26 21:04 ` David Woodhouse
2003-10-26 20:54 ` Charles Manning
2003-10-27 8:34 ` Nikita Danilov
2003-10-27 8:39 ` David Woodhouse
2003-10-27 8:43 ` Nikita Danilov
2003-10-27 8:46 ` David Woodhouse
2003-10-27 8:52 ` Nikita Danilov
2003-10-27 9:06 ` David Woodhouse
2003-10-27 9:08 ` David Woodhouse
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=1065552897.8172.28.camel@patehci2 \
--to=p.lavarre@ieee.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=zachary@cse.ucsc.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