From: Bill Davidsen <davidsen@tmr.com>
To: Neil Brown <neilb@suse.de>
Cc: Marcin Krol <admin@domeny.pl>, linux-raid@vger.kernel.org
Subject: Re: Deleting mdadm RAID arrays
Date: Wed, 06 Feb 2008 14:03:27 -0500 [thread overview]
Message-ID: <47AA047F.9060507@tmr.com> (raw)
In-Reply-To: <18344.49968.584648.904844@notabene.brown>
Neil Brown wrote:
> On Tuesday February 5, admin@domeny.pl wrote:
>
>> % mdadm --zero-superblock /dev/sdb1
>> mdadm: Couldn't open /dev/sdb1 for write - not zeroing
>>
>
> That's weird.
> Why can't it open it?
>
>
I suspect that (a) he's not root and has read-only access to the device
(I have group read for certain groups, too). And since he had the arrays
on raw devices, shouldn't he zero the superblocks using the whole device
as well? Depending on what type of superblock it might not be found
otherwise.
It sure can't hurt to zero all the superblocks of the whole devices and
then check the partitions to see if they are present, then create the
array again with --force and be really sure the superblock is present
and sane.
> Maybe you aren't running as root (The '%' prompt is suspicious).
> Maybe the kernel has been told to forget about the partitions of
> /dev/sdb.
> mdadm will sometimes tell it to do that, but only if you try to
> assemble arrays out of whole components.
>
> If that is the problem, then
> blockdev --rereadpt /dev/sdb
>
> will fix it.
>
> NeilBrown
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
next prev parent reply other threads:[~2008-02-06 19:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 10:42 Deleting mdadm RAID arrays Marcin Krol
2008-02-05 11:43 ` Moshe Yudkowsky
2008-02-06 9:35 ` Marcin Krol
2008-02-05 12:27 ` Janek Kozicki
2008-02-05 13:52 ` Michael Tokarev
2008-02-05 14:33 ` Moshe Yudkowsky
2008-02-05 15:16 ` Michael Tokarev
2008-02-05 14:47 ` Auto generation of mdadm.conf (was: Deleting mdadm RAID arrays) Janek Kozicki
2008-02-05 15:34 ` Auto generation of mdadm.conf Michael Tokarev
2008-02-05 18:39 ` Janek Kozicki
2008-02-05 20:12 ` Deleting mdadm RAID arrays Neil Brown
2008-02-06 9:55 ` Marcin Krol
2008-02-06 10:11 ` Peter Rabbitson
2008-02-06 10:32 ` Marcin Krol
2008-02-06 10:43 ` Neil Brown
2008-02-06 12:03 ` Marcin Krol
2008-02-07 2:36 ` Neil Brown
2008-02-07 9:56 ` Marcin Krol
2008-02-07 21:35 ` Bill Davidsen
2008-02-08 9:35 ` Marcin Krol
2008-02-08 12:44 ` Bill Davidsen
2008-02-08 12:52 ` Marcin Krol
2008-02-06 19:03 ` Bill Davidsen [this message]
2008-02-06 11:22 ` David Greaves
2008-02-06 11:56 ` Marcin Krol
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=47AA047F.9060507@tmr.com \
--to=davidsen@tmr.com \
--cc=admin@domeny.pl \
--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).