From: berk walker <berk@panix.com>
To: Jon@eHardcastle.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Thrashing a drive to flush out problems..
Date: Mon, 25 Jan 2010 10:02:02 -0500 [thread overview]
Message-ID: <4B5DB26A.9070404@panix.com> (raw)
In-Reply-To: <77733.15823.qm@web51302.mail.re2.yahoo.com>
Jon Hardcastle wrote:
> Hi guys can anyone recommend a tool for thrashing the b*ll*cks of a drive in way that isn't destructive to the data?
>
> I was thinking badblocks with -w but it is destructive and i dont want to do anything that will potentially lower the integrity of my array? (Even tho it is raid6 :) )
>
> There must be some bonnie esk tool that will read/write every combination to every block but keep the data safe after to flush out any sector issues etc.
>
> Cheers.
>
>
> -----------------------
> N: Jon Hardcastle
> E: Jon@eHardcastle.com
> 'Do not worry about tomorrow, for tomorrow will bring worries of its own.'
>
> ***********
> Please note, I am phasing out jd_hardcastle AT yahoo.com and replacing it with jon AT eHardcastle.com
> ***********
>
> -----------------------
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
Thirty-some years ago, I used to use multiple instances of disk
access/read routines. As the areas wrapped around the last cylinder and
restarted from zero, all lengths and frequency of seeks took place.
Of course, in those days, drives were physically huge, tracks wide and
few. I used to run the tests for Jaquard Systems, on occasion. Drives
sounded like they were gong to fly apart. Never did find a bad one that
way, tho-
b-
next prev parent reply other threads:[~2010-01-25 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 14:26 Thrashing a drive to flush out problems Jon Hardcastle
2010-01-25 15:02 ` berk walker [this message]
2010-01-26 11:47 ` Julian Cowley
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=4B5DB26A.9070404@panix.com \
--to=berk@panix.com \
--cc=Jon@eHardcastle.com \
--cc=linux-raid@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).