From: Nikita Danilov <Nikita@Namesys.COM>
To: linux-kernel@vger.kernel.org
Cc: folkert@vanheusden.com, Rik van Riel <riel@conectiva.com.br>
Subject: Re: tool for testing how fast your kernel can rename files :-)
Date: Tue, 21 Jan 2003 12:13:27 +0300 [thread overview]
Message-ID: <15917.3895.100193.906443@laputa.namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.50L.0301202342390.18171-100000@imladris.surriel.com>
Rik van Riel writes:
> On Mon, 20 Jan 2003 folkert@vanheusden.com wrote:
>
> > This night, while half a-sleep I thought it is usefull to have a tool
> > which creates a number of files in a directory and then starts to
> > randomly rename them.
>
> > But now, fully awake with at least 8 cups of coffee in my system I cannot
> > think of anything usefull this program is actually doing.
> > Well, maybe to test if something gets corrupted allong the way?
>
> You could test with NFS, you might even break something...
Now, when NFS has been mentioned.
To test reiser{fs,4} we use
ftp://ftp.namesys.com/pub/namesys-utils/nfs_fh_stale.c which creates
given number of threads each performing randomly reads, writes,
truncates, renames, fsyncs, and unlinks over the shared set of files. As
its name implies it was initially created to test support for the stale
NFS handle detection, but turned out to be quite useful for the general
testing also.
>
> Rik
Nikita.
prev parent reply other threads:[~2003-01-21 9:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 17:29 folkert
2003-01-20 17:54 ` Andreas Dilger
2003-01-20 20:36 ` Cliff White
2003-01-20 21:11 ` Folkert van Heusden
2003-01-21 1:43 ` Rik van Riel
2003-01-21 9:13 ` Nikita Danilov [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=15917.3895.100193.906443@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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
all inboxes | Powered by JetHome®