From: "P.V.Anthony" <pvantony@singnet.com.sg>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Hard Drive Stress Test Application
Date: Tue, 01 May 2007 22:35:41 +0800 [thread overview]
Message-ID: <4637503D.2040307@singnet.com.sg> (raw)
In-Reply-To: <20070426135306.GA83846@sgi.com>
On this day, 26-April-2007 9:53 PM, Bob Sanders wrote:
> P.V.Anthony, mused, then expounded:
>> Now I need to test to see if it works under stress conditions for my
>> hard disks.
>>
>
> Give xdd a try - http://www.ioperformance.com/
>
> It's scriptable, works on single drives as well as huge NAS setups.
> And it's an accepted benchmarking tool.
Thank you for the link.
I am using it now and am happy with it.
Once again thank you.
P.V.Anthony
--
gentoo-amd64@gentoo.org mailing list
prev parent reply other threads:[~2007-05-01 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 3:08 [gentoo-amd64] Hard Drive Stress Test Application P.V.Anthony
2007-04-26 3:33 ` Joshua Hoblitt
2007-04-26 3:45 ` Peter Davoust
2007-04-26 14:07 ` P.V.Anthony
2007-04-26 3:42 ` Daniel Iliev
2007-04-26 3:45 ` Drew
2007-04-26 3:58 ` Wil Reichert
2007-04-26 12:28 ` [gentoo-amd64] " Duncan
2007-04-26 13:53 ` [gentoo-amd64] " Bob Sanders
2007-05-01 14:35 ` P.V.Anthony [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=4637503D.2040307@singnet.com.sg \
--to=pvantony@singnet.com.sg \
--cc=gentoo-amd64@lists.gentoo.org \
/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