From: NeilBrown <neilb@suse.de>
To: lrhorer@satx.rr.com
Cc: 'Linux RAID' <linux-raid@vger.kernel.org>
Subject: Re: OK, Now this is really weird
Date: Sun, 27 Feb 2011 18:57:04 +1100 [thread overview]
Message-ID: <20110227185704.18777dfa@notabene.brown> (raw)
In-Reply-To: <C3.E3.07087.0CBF96D4@cdptpa-omtalb.mail.rr.com>
On Sun, 27 Feb 2011 01:22:41 -0600 "Leslie Rhorer" <lrhorer@satx.rr.com>
wrote:
>
> > > >> > So what gives? /dev/sdk3 no longer even exists, so why hasn't
> > it
> > > >> > been failed and removed on /dev /md3 like it has on /dev/md1 and
> > > >> /dev/md2?
> > > >>
> > > >> Is it possible there has been no I/O request for /dev/md3 since
> > > >> /dev/sdk failed?
> > > >
> > > > Well, I thought about that. It's swap space, so I suppose it's
> > > > possible. I would have thought, however, that mdadm would fail a
> > missing
> > > > member whether there is any I/O or not.
> > > >
> > > > --
> > > > 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
> > > >
> > >
> > > I thought so as well. But how will mdadm know is the device is faulty,
> > > unless the device is generating errors? (which usually only happens on
> > > read and/or write)
> >
> > With very recent mdadm the command
> >
> > mdadm -If sdXX
> >
> > will find any md array that has /dev/sdXX as a member and will fail and
> > remove it.
>
> No, it's version 3.1.4, and that gives me a "Device or Resource
> busy" error. It does report that it set sdk3 faulty, but the hot remove
> fails.
>
> So how can I remove the drive (so I can add it back)?
Maybe:
mdadm /dev/md2 --remove failed
NeilBrown
--
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
next prev parent reply other threads:[~2011-02-27 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 7:00 OK, Now this is really weird Leslie Rhorer
2011-02-26 7:36 ` Jeff Woods
2011-02-26 11:20 ` Leslie Rhorer
2011-02-26 11:35 ` Mathias Burén
2011-02-26 21:34 ` NeilBrown
2011-02-27 7:22 ` Leslie Rhorer
2011-02-27 7:57 ` NeilBrown [this message]
2011-02-27 7:15 ` Leslie Rhorer
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=20110227185704.18777dfa@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.com \
/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