From: Neil Brown <neilb@suse.de>
To: thomas62186218@aol.com
Cc: linux-raid@vger.kernel.org
Subject: Re: /sys/block/md0 still present after mdadm -S and -r
Date: Mon, 13 Oct 2008 11:56:50 +1100 [thread overview]
Message-ID: <18674.40146.187485.200241@notabene.brown> (raw)
In-Reply-To: message from thomas62186218@aol.com on Friday September 26
On Friday September 26, thomas62186218@aol.com wrote:
> Hi All,
>
> I created an md device as follows:
>
> mdadm -C -f -e 1.0 -R /dev/md0 -l 0 -n 2 -c 32 /dev/sdc1 /dev/sdg1
>
> It was successful and started.
>
> I then want to delete this md device and did as follows:
>
> mdadm -S /dev/md0
> mdadm /dev/md0 -r
> mdadm --zero-superblock /dev/sdc1
> mdadm --zero-superblock /dev/sdg1
>
> I did not receive any errors. Afterwards, md0 was no longer visible in
> /proc/mdstat.
>
> However, there is still /sys/block/md0 entry, as well as an /dev/md0
> entry. I would have expected these to be gone.
>
> Is my md0 not getting fully deleted?
The array is completely gone. That fact that you can still see
/sys/block/md0 is an implementation artifact. It is very difficult to
make it go away in a race-free way, and there is little cost is
leaving it there.
NeilBrown
prev parent reply other threads:[~2008-10-13 0:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 13:28 /sys/block/md0 still present after mdadm -S and -r thomas62186218
2008-10-13 0:56 ` Neil Brown [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=18674.40146.187485.200241@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=thomas62186218@aol.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