From: Phil Turmel <philip@turmel.org>
To: "Miguel Corberán Ruiz" <migcorrui@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Problem halting raid 1
Date: Fri, 06 Sep 2013 07:38:01 -0400 [thread overview]
Message-ID: <5229BE99.4070701@turmel.org> (raw)
In-Reply-To: <CABcjxUOszUPsEJu_nCSRwzCCy5ijs9YUb0ia8HbZ6kzW-jCwWA@mail.gmail.com>
Good morning Miguel,
On 09/06/2013 06:42 AM, Miguel Corberán Ruiz wrote:
> Hello,
> I am having a problem stopping an array. When I use the command "mdadm
> --stop /dev/md0" the array disappears completely. It does not even
> appear under /dev/m..
This is the expected behavior.
> Then, when I try "mdadm --remove /dev/md0" bash tells me that /dev/md0
> does not exist. So, after stopping the array with "mdadm --stop ..",
> "cat /proc/mdstat" says that there is no array running. From what I
> read the array should be visible but in a halted/stopped/deactivated
> state. And then one can proceed to remove it.
The --remove action is used to remove a failed member from an array, not
an array itself.
> What I want to do is to completely remove the array so I can mount the
> individual partitions anywhere else without the need of mdadm (and
> access the data created when the array was running).
You would use --zero-superblock on each member device to make it
"forget" what array it belonged to.
HTH,
Phil
--
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:[~2013-09-06 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 10:42 Problem halting raid 1 Miguel Corberán Ruiz
2013-09-06 11:38 ` Phil Turmel [this message]
[not found] ` <CABcjxUMBp=oZ7Dg65ZK4ft-Jix4kAi=VV3juE1KWRkw8RnYKyQ@mail.gmail.com>
2013-09-06 12:18 ` Phil Turmel
2013-09-06 12:19 ` NeilBrown
2013-09-06 16:09 ` Tregaron Bayly
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=5229BE99.4070701@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=migcorrui@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.