From: NeilBrown <neilb@suse.de>
To: "Miguel Corberán Ruiz" <migcorrui@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Problem halting raid 1
Date: Fri, 6 Sep 2013 22:19:05 +1000 [thread overview]
Message-ID: <20130906221905.0eb57dc5@notabene.brown> (raw)
In-Reply-To: <CABcjxUOszUPsEJu_nCSRwzCCy5ijs9YUb0ia8HbZ6kzW-jCwWA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
On Fri, 6 Sep 2013 12:42:23 +0200 Miguel Corberán Ruiz <migcorrui@gmail.com>
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..
>
> 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.
>
> 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).
If the array uses 0.90 or 1.0 metadata, then having stopped the array you can
simply mount the component devices
If it uses 1.1 or 1.2 you can only access the data via md.
The version is listed at the top of "mdadm --examine /dev/sdXX" or "mdadm
--detail /dev/md0" output.
NeilBrown
>
> Any help will be appreciated. Thank you in advance,
> Miguel
> --
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-09-06 12:19 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
[not found] ` <CABcjxUMBp=oZ7Dg65ZK4ft-Jix4kAi=VV3juE1KWRkw8RnYKyQ@mail.gmail.com>
2013-09-06 12:18 ` Phil Turmel
2013-09-06 12:19 ` NeilBrown [this message]
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=20130906221905.0eb57dc5@notabene.brown \
--to=neilb@suse.de \
--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 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).