mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Johan Groth <johan.groth@linux-grotto.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scsi errors with Megaraid 300-8x
Date: Wed, 23 Aug 2006 11:59:06 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0608231158210.15031@p34.internal.lan> (raw)
In-Reply-To: <44EC7AFD.2070605@linux-grotto.org.uk>



On Wed, 23 Aug 2006, Johan Groth wrote:

> Justin Piszcz wrote:
>> 
>> Nope, r+w will write over everything on the disk, but I have found -the- 
>> most effective way to see if a disk is good or not.  I'd rather have the 
>> disk die to that test rather than using it in production and finding it 
>> dies with my data on it.
>> 
>
> Hmm, we both should read the man page of badblocks a bit better :).
> I found this:
>
> -n     Use non-destructive read-write mode.  By default only a 
> non-destructive read-only test is done. This option must not be combined with 
> the -w option, as they are mutually exclusive.
>
>
> Cheers,
> Johan
>

I have not tested that option.  I wonder if it is as good as a real R+W 
mode.  What does smartctl -a /dev/sda say on the disk that you are having 
problems with?

  reply	other threads:[~2006-08-23 15:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 14:45 Johan Groth
2006-08-23 15:27 ` Mark Lord
2006-08-23 15:42   ` Johan Groth
2006-08-23 15:45     ` Justin Piszcz
2006-08-23 15:48       ` Johan Groth
2006-08-23 15:53         ` Justin Piszcz
2006-08-23 15:57           ` Johan Groth
2006-08-23 15:59             ` Justin Piszcz [this message]
2006-08-24 14:48         ` Mark Lord
2006-08-24 15:09           ` Johan Groth
2006-08-24 16:57             ` Mark Lord

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=Pine.LNX.4.64.0608231158210.15031@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=johan.groth@linux-grotto.org.uk \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®