From: Harry Mangalam <hjm@moo.nac.uci.edu>
To: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: How to free devices held captive by failed arrays
Date: Fri, 21 Oct 2011 16:08:24 -0700 [thread overview]
Message-ID: <20111021230824.GA11647@moo.nac.uci.edu> (raw)
In-Reply-To: <20111022100457.0f5133f3@notabene.brown>
> > > >
> > > >
> > > > What do I have to do to free this device?
> > >
> > > Doesn't
> > >
> > > mdadm --stop /dev/md_d0
> > >
> > > release sdg1 ??
> > >
> > > NeilBrown
> >
> > No, it doesn't.
> >
> > $ mdadm --stop /dev/md_d0
> > mdadm: error opening /dev/md_d0: No such file or directory
> >
> > In fact, that's sort of odd:
> >
> > $ ls -l /dev/md*
> > brw-rw---- 1 root disk 9, 0 2011-10-20 17:18 /dev/md0
> > lrwxrwxrwx 1 root root 7 2011-10-20 17:05 /dev/md_d0p1 -> md/d0p1
> > lrwxrwxrwx 1 root root 7 2011-10-20 17:05 /dev/md_d0p2 -> md/d0p2
> > lrwxrwxrwx 1 root root 7 2011-10-20 17:05 /dev/md_d0p3 -> md/d0p3
> > lrwxrwxrwx 1 root root 7 2011-10-20 17:05 /dev/md_d0p4 -> md/d0p4
> >
> > /dev/md:
> > total 0
> > brw------- 1 root root 254, 0 2011-10-20 17:05 d0
> > brw------- 1 root root 254, 1 2011-10-20 17:05 d0p1
> > brw------- 1 root root 254, 2 2011-10-20 17:05 d0p2
> > brw------- 1 root root 254, 3 2011-10-20 17:05 d0p3
> > brw------- 1 root root 254, 4 2011-10-20 17:05 d0p4
> >
> > [no record of /dev/md_d0] ...?
> >
> > hjm
> >
>
> md_d0 is another name for md/d0. The former probably only gets created when
> the array becomes active.
> So use
> mdadm --stop /dev/md/d0
Perfect! That did it. The other RAID is now initializing.
That goes in the personal HowTos..
Many thanks!
hjm
prev parent reply other threads:[~2011-10-21 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 20:27 How to free devices held captive by failed arrays Harry Mangalam
2011-10-21 22:41 ` NeilBrown
2011-10-21 22:45 ` Harry Mangalam
2011-10-21 23:04 ` NeilBrown
2011-10-21 23:08 ` Harry Mangalam [this message]
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=20111021230824.GA11647@moo.nac.uci.edu \
--to=hjm@moo.nac.uci.edu \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).