From: Martin Wilck <mwilck@arcor.de>
To: linux-raid@vger.kernel.org, NeilBrown <neilb@suse.de>
Subject: mdadm -Db switches array to write-pending?!
Date: Wed, 10 Jul 2013 19:54:09 +0200 [thread overview]
Message-ID: <51DD9FC1.2060200@arcor.de> (raw)
Hi Neil, hi all,
I discovered a weird behavior of mdadm -Db - it will switch a RAID array
from read-auto state to write-pending. For DDF (and possibly other
formats) this will cause metadata writes.
If I read the code correctly, the reason is that mdadm -Db will use the
GET_BITMAP_FILE ioctl, which calls md_allow_write(). I saw this on a
CentOS 6.3 kernel but comparing the code I didn't see a difference in
recent kernels.
I am wondering if this is intentional, and if no, if anything could be
done about it. It is certainly surprising behavior.
Regards
Martin
next reply other threads:[~2013-07-10 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 17:54 Martin Wilck [this message]
2013-07-15 5:18 ` mdadm -Db switches array to write-pending?! NeilBrown
2013-07-17 20:19 ` Martin Wilck
2013-07-26 18:01 ` Martin Wilck
2013-07-26 21:58 ` NeilBrown
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=51DD9FC1.2060200@arcor.de \
--to=mwilck@arcor.de \
--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).