linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Derek Vadala <derek@cynicism.com>
Cc: Linux-Raid <linux-raid@vger.kernel.org>
Subject: Re: Manually fail a disk?
Date: Sun, 19 Jan 2003 16:08:59 -0500	[thread overview]
Message-ID: <20030119210859.GB18651@rdlg.net> (raw)
In-Reply-To: <20030119144321.D9B7E3B808@jaded.cynicism.com>

[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]



raidsetsetfaulty gave back an error (scrolled off the screen and the
machine has since seized up.  raidhotremove pretty much hung up trying
to get disk access.  I was hoping I could tell the kernel or the md
driver to mark it bad and take it out of the array.


Thus spake Derek Vadala (derek@cynicism.com):

> >   I've got a disk that's starting to fail hard.  It's generating alot of
> > errors in dmesg and /var/log/messages.  If the raid disk gets any usage
> > it'll lock up the box it's spewing errors so fast.  I can't get out to
> > physically yank the disk until Tues but need it off-lined now.  Is there
> > a way to tell mdtools (version 0.42-33) to mark a disk faulty and not
> > use it?
> 
> I'll assume this is a RAID-1 or RAID-5 and that you're not trying this on
> a non-redundant array...
> 
> 
> # mdadm /dev/md0 --fail /dev/sda1
> # mdadm /dev/md0 --remove /dev/sda1
> 
> The first command fails /dev/sda1 (a member of /dev/md0) and the second
> command removes it from /dev/md0.
> 
> If you are using raidtools try:
> 
> # raidsetfaulty /dev/md0 /dev/sda1
> # raidhotremove /dev/md0 /dev/sda1
> 
> --
> Derek Vadala, derek@cynicism.com, http://www.cynicism.com/~derek
> 
> -
> 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



:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | PGP Key ID: FC96D405
                               
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.
FYI:
 perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-01-19 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19 13:29 Manually fail a disk? Robert L. Harris
2003-01-19 14:43 ` Derek Vadala
2003-01-19 21:08   ` Robert L. Harris [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-20 19:46 Cress, Andrew R

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=20030119210859.GB18651@rdlg.net \
    --to=robert.l.harris@rdlg.net \
    --cc=derek@cynicism.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).