From: Martin Cracauer <cracauer@cons.org>
To: linux-raid@vger.kernel.org
Subject: Superblock V 1.2
Date: Sun, 7 Nov 2010 14:15:07 -0500 [thread overview]
Message-ID: <20101107191507.GA31052@cons.org> (raw)
I created a new array after upgrading kernel and OS
(2.6.32.25-cracauer and Debian/squeeze, respectively, resulting in
mdadm - v3.1.4 - 31st August 2010)
The new array reads
md0 : active raid5 sdc2[4] sda2[2] sdb2[1] sdd2[0]
292998144 blocks super 1.2 level 5, 256k chunk, algorithm 2 [4/4] [UUUU]
I figure the "super 1.2" means the new version of the superblock.
Can I read that array if I ever connect the machine to an older
kernel/mdadm? I see that I can control which version to use in
mdadm(8), but I don't get what the advantage of the new format is if I
don't run out of # of components or total capacity. I can see how
storing the superblock at 4 KB makes it more robust against accidents
that wipe out of the first 512 bytes or similar fun. I think storing
it at the end will be a pain if you ever have to hexdump recover the
thing, no?
I also wonder why this is the only version announced in /proc/mdstat
if it is what is now the default? Shouldn't it announce the v0.9
blocks?
Is anybody here using the DDF format? I don't plan to get hardware
raid but why not prepare for it?
Thanks
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
next reply other threads:[~2010-11-07 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 19:15 Martin Cracauer [this message]
2010-11-07 21:03 ` Superblock V 1.2 Leslie Rhorer
2010-11-07 21:08 ` Martin Cracauer
2010-11-07 21:39 ` John Robinson
2010-11-09 16:35 ` Martin Cracauer
2010-11-09 17:08 ` John Robinson
2010-11-15 1:11 ` Neil Brown
2010-11-15 16:16 ` Martin Cracauer
2010-11-15 19:47 ` Neil Brown
2010-11-15 19:52 ` Martin Cracauer
2010-11-15 20:11 ` Neil Brown
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=20101107191507.GA31052@cons.org \
--to=cracauer@cons.org \
--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).