From: Ben Winslow <rain@bluecherry.net>
To: linux-raid@vger.kernel.org
Subject: Autostarting arrays with V1 metadata
Date: Wed, 07 May 2008 14:03:39 -0400 [thread overview]
Message-ID: <4821EEFB.1040501@bluecherry.net> (raw)
I've noticed that (as of 2.6.25, at least) the kernel doesn't autostart
arrays with V1 metadata. In autostart_arrays(), md_import_device() is
called for 0.90 arrays only, and there's currently no sort of
autodetection of the superblock position for V1 metadata.
Is this simply a matter of the code being unwritten, or are there other
reasons that V1 arrays aren't autostarted (such as the SB format being
unfinished)? My only real motivation to use V1 metadata is the unhashed
homehost field, which I'll give up if the SB format hasn't stabilized yet.
Thanks,
--
Ben Winslow <rain@bluecherry.net>
next reply other threads:[~2008-05-07 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 18:03 Ben Winslow [this message]
2008-05-08 3:05 ` Autostarting arrays with V1 metadata Neil Brown
2008-05-08 14:50 ` Bryan Mesich
2008-05-08 8:19 ` David Greaves
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=4821EEFB.1040501@bluecherry.net \
--to=rain@bluecherry.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).