linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID1 assembled broken array
Date: Sat, 26 Sep 2009 14:01:00 +0100	[thread overview]
Message-ID: <4ABE108C.9030606@anonymous.org.uk> (raw)
In-Reply-To: <20090926095834.GP5174@skl-net.de>

On 26/09/2009 10:58, Andre Noll wrote:
> On 18:12, Neil Brown wrote:
>>> BTW: Why are new arrays still created with 0.90 metadata format by
>>> default?
>> Because I'm a chicken....
>>
>> I guess it probably is time ... but to we make the default 1.0, which
>> is compatible with people's expectations, to 1.1 which is generally a
>> safer approach (you cannot mount a bare device by mistake).
> 
> People will soon have to use 1.x anyway as drives are getting bigger
> than 2T. I'd vote for making 1.1 or 1.2 metadata the default for the
> reasons Doug pointed out. Failing to mount the bare device if there
> is a partition table is IMHO more important than meeting (broken)
> expectations.
> 
> Maybe we should depricate kernel-level autodetection at the same time
> so that using an initramfs becomes mandatory for setups with / on md.

It already is deprecated; afaik all the recent distros already use an 
initramfs, even if they still use 0.90 metadata.

I second making this a priority to get into the next round of distro 
updates, for all the reasons given. As soon as metadata version upgrade 
facilities go in to mdadm, 0.90 metadata can also be deprecated and 
perhaps mdadm can issue warnings, or at least the kernel autoassembly 
code can start issuing warnings (if it doesn't already).

Cheers,

John.

  reply	other threads:[~2009-09-26 13:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 19:22 RAID1 assembled broken array Matthias Urlichs
2009-09-15 19:24 ` Majed B.
2009-09-15 19:33   ` Matthias Urlichs
2009-09-15 19:43     ` Majed B.
2009-09-15 20:04       ` Doug Ledford
2009-09-15 20:00 ` Doug Ledford
2009-09-15 20:27   ` Matthias Urlichs
2009-09-15 21:01   ` NeilBrown
2009-09-16  4:50     ` Matthias Urlichs
2009-09-17 16:44       ` Doug Ledford
2009-09-17 17:09         ` Matthias Urlichs
2009-09-17 17:12           ` Majed B.
2009-09-25  8:07           ` Neil Brown
2009-09-17  8:25     ` Andre Noll
2009-09-25  8:12       ` Neil Brown
2009-09-25 10:42         ` Chris Webb
2009-09-26  9:58         ` Andre Noll
2009-09-26 13:01           ` John Robinson [this message]
2009-09-26 19:21             ` Clinton Lee Taylor
2009-09-28 16:12               ` Andre Noll

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=4ABE108C.9030606@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --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).