From: seth vidal <skvidal@phy.duke.edu>
To: Luca Berra <bluca@comedia.it>
Cc: linux-raid@vger.kernel.org
Subject: Re: disk failure and badblocks
Date: Sat, 22 Nov 2003 09:57:36 -0500 [thread overview]
Message-ID: <1069513055.4351.8.camel@binkley> (raw)
In-Reply-To: <20031122141218.GF12265@percy.comedia.it>
On Sat, 2003-11-22 at 09:12, Luca Berra wrote:
> On Sat, Nov 22, 2003 at 03:22:21AM -0500, seth vidal wrote:
> >My major wonder is will badblocks be effective for looking for a medium
> >error?
> only if you can disable the disk onboard cache :)
> a long time ago i changed badblocks write mode algo to write a pattern
> to the full disk THEN check it, instead of write-block, check, next
> block which was a victim of the cache. Pity i lost that patch :)
What if I made the number of blocks written at any time * the block byte
size greater than the onboard disk cache? That seems like it might
circumvent the caching problem.
-sv
next prev parent reply other threads:[~2003-11-22 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-22 8:22 disk failure and badblocks seth vidal
2003-11-22 14:12 ` Luca Berra
2003-11-22 14:57 ` seth vidal [this message]
2003-11-22 15:19 ` Luca Berra
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=1069513055.4351.8.camel@binkley \
--to=skvidal@phy.duke.edu \
--cc=bluca@comedia.it \
--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).