From: NeilBrown <neilb@suse.de>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: failed to write superblock errors, and more!
Date: Tue, 15 Feb 2011 15:24:36 +1100 [thread overview]
Message-ID: <20110215152436.1351c219@notabene.brown> (raw)
In-Reply-To: <AANLkTinedfgQ5xjqKvM_v3Y6D2Fz=Eq0H1ZjmTcLuz+C@mail.gmail.com>
On Mon, 14 Feb 2011 22:00:46 -0600 Jon Nelson
<jnelson-linux-raid@jamponi.net> wrote:
> I'm wondering what's going on here:
>
> turnip:~ # mdadm /dev/md1 --create --level=1 --bitmap=internal
> --raid-devices=2 /dev/sdd1 missing
> mdadm: array /dev/md1 started.
So far, so good.
> turnip:~ # mdadm /dev/md2 --create --level=1 --bitmap=internal
> --raid-devices=2 /dev/md1 missing
> mdadm: failed to write superblock to /dev/md1
Probably your device is an exact multiple of 64K in size, and is of such a
size that mdadm choose a bitmap size between 60K and 64K. This doesn't fit
and initialising the bitmap fail. Fixed in newer releases.
> mdadm: array /dev/md2 started.
oops. mdadm ignores the error status after printing the 'failed to write
superblock' message. Note added to my to-do list.
> turnip:~ # mdadm /dev/md2 --stop
Normal usage is:
mdadm --stop /dev/md2
Putting them in the other order should either work or give an error message.
It currently does neither. Note added to my to-do list.
Remaining messages are because /dev/md2 is not stopped.
NeilBrown
> turnip:~ # mdadm --zero-superblock /dev/md1
> mdadm: Couldn't open /dev/md1 for write - not zeroing
> turnip:~ # mdadm /dev/md1 --stop
> turnip:~ # mdadm --zero-superblock /dev/sdd1
> mdadm: Couldn't open /dev/sdd1 for write - not zeroing
> turnip:~ # mdadm /dev/md2 --stop
> turnip:~ # mdadm /dev/md2 --stop --force
> turnip:~ # ls /sys/block/md1/holders/
> md2
> turnip:~ #
>
> The kernel is 2.6.34.7-0.7-default (x86_64). openSUSE 11.3.
> mdadm 3.0.3
>
prev parent reply other threads:[~2011-02-15 4:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 4:00 failed to write superblock errors, and more! Jon Nelson
2011-02-15 4:24 ` NeilBrown [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=20110215152436.1351c219@notabene.brown \
--to=neilb@suse.de \
--cc=jnelson-linux-raid@jamponi.net \
--cc=linux-raid@vger.kernel.org \
/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).