From: PGNet <pgnet.trash+raid@gmail.com>
To: linux-raid@vger.kernel.org
Subject: mdadm "--examine" & "--detail" report different metadata version info for same array
Date: Sun, 19 Apr 2009 22:27:47 -0700 [thread overview]
Message-ID: <dbd51810904192227k6d0a8796y79156765839c1e84@mail.gmail.com> (raw)
running openSUSE 11.1,
uname -ri
2.6.27.21-27-xen x86_64
with,
mdadm --version
mdadm - v3.0-devel2 - 5th November 2008
creating a raid array with mdadm, e.g.
mdadm -v --create /dev/md0 --level=raid10 --raid-devices=2
--layout=f2 --chunk=1024 --metadata=1.2 --bitmap=internal /dev/sda1
/dev/sdb1
checking array data from superblocks,
mdadm --examine --scan
ARRAY /dev/md/0 level=raid10 metadata=1.2 num-devices=2 UUID=138... name=nas:0
and active array,
mdadm --detail --scan
ARRAY /dev/md0 level=raid10 num-devices=2 metadata=1.02 name=nas:0 UUID=138...
reports two different metadata versions -- "1.02" and "1.2"
why are the two #s different? convention, or bug?
thanks.
reply other threads:[~2009-04-20 5:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=dbd51810904192227k6d0a8796y79156765839c1e84@mail.gmail.com \
--to=pgnet.trash+raid@gmail.com \
--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).