From: Neil Brown <neilb@suse.de>
To: Giovanni Tessore <giotex@texsoft.it>
Cc: linux-raid@vger.kernel.org
Subject: Re: Linux mdadm superblock question.
Date: Thu, 18 Feb 2010 10:10:35 +1100 [thread overview]
Message-ID: <20100218101035.3a104fed@notabene.brown> (raw)
In-Reply-To: <4B7A6FA3.5080009@texsoft.it>
On Tue, 16 Feb 2010 11:12:51 +0100
Giovanni Tessore <giotex@texsoft.it> wrote:
> Neil Brown wrote:
> > When mdadm defaults to 1.0 for a RAID1 it prints a warning to the effect that
> > the array might not be suitable to store '/boot', and requests confirmation.
> >
> > So I assume that the people who are having this problem either do not read,
> > or are using some partitioning tool that runs mdadm under the hood using
> > "--run" to avoid the need for confirmation. It would be nice to confirm if
> > that was the case, and find out what tool is being used.
> >
>
> I created it manually with
> mdadm --create /dev/md0 --metadata=1.0 --level=1 --raid-devices=3
> /dev/sd[abc]1
> but got no warning or confirmation request (mdadm - v2.6.7.1 - 15th
> October 2008), I guess due to old version.
>
No - due to your actions not matching my description.
I said "when mdadm defaults to 1.0", though I should have said
"...defaults to 1.1". Sorry about that.
In any case, you didn't let it default to anything, so you presumably know
what you are doing.
And no v2.6.7.1 will never default to 1.1 so it will never give the message.
But v3.1.1 will default to 1.1 and when it does, it will print the message.
NeilBrown
> Regards
>
next prev parent reply other threads:[~2010-02-17 23:10 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 23:00 Linux mdadm superblock question Justin Piszcz
2010-02-12 1:52 ` Michael Evans
2010-02-12 9:06 ` Robin Hill
2010-02-12 21:53 ` Mr. James W. Laferriere
2010-02-16 0:57 ` Neil Brown
2010-02-16 16:42 ` Bill Davidsen
2010-02-13 19:58 ` H. Peter Anvin
2010-02-13 20:07 ` Justin Piszcz
2010-02-13 20:49 ` david
2010-02-13 21:07 ` Michael Evans
2010-02-13 21:29 ` H. Peter Anvin
2010-02-14 20:25 ` Asdo
2010-02-14 21:18 ` H. Peter Anvin
2010-02-14 21:34 ` Henrique de Moraes Holschuh
2010-02-14 23:20 ` Rudy Zijlstra
2010-02-15 3:40 ` Mr. James W. Laferriere
2010-02-15 7:12 ` Luca Berra
2010-02-16 0:38 ` Neil Brown
2010-02-16 0:27 ` Neil Brown
2010-02-16 1:24 ` H. Peter Anvin
2010-02-16 3:18 ` david
2010-02-16 4:42 ` John Robinson
2010-02-16 7:02 ` H. Peter Anvin
2010-02-16 8:46 ` Rudy Zijlstra
2010-02-16 17:05 ` Bill Davidsen
2010-02-16 23:30 ` H. Peter Anvin
2010-02-16 10:12 ` Giovanni Tessore
2010-02-17 23:10 ` Neil Brown [this message]
2010-02-16 3:40 ` CaT
2010-02-13 6:42 ` martin f krafft
2010-02-13 8:37 ` Giovanni Tessore
2010-02-13 9:26 ` Michael Evans
2010-02-13 9:35 ` Giovanni Tessore
2010-02-13 9:40 ` Michael Evans
2010-02-13 10:06 ` Giovanni Tessore
2010-02-16 0:50 ` Neil Brown
2010-02-16 13:14 ` Justin Piszcz
2010-02-16 20:09 ` mdadm FAQ (was: Linux mdadm superblock question.) martin f krafft
2010-02-17 23:11 ` Linux mdadm superblock question Neil Brown
2010-02-16 17:24 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2010-02-14 1:51 Volker Armin Hemmann
2010-02-14 4:02 ` Michael Evans
2010-02-14 7:21 ` david
2010-02-14 8:38 ` Michael Evans
2010-02-14 18:40 ` Volker Armin Hemmann
2010-02-14 18:53 ` John Robinson
2010-02-14 21:16 ` Gabor Gombas
[not found] ` <201002142013.24922.volkerarmin@googlemail.com>
2010-02-16 14:28 ` John Robinson
2010-02-16 14:37 ` Volker Armin Hemmann
2010-02-16 14:46 ` Robin Hill
2010-02-16 17:23 ` John Robinson
2010-02-16 19:38 ` Luca Berra
2010-02-16 17:18 ` Bill Davidsen
2010-02-16 21:06 ` Volker Armin Hemmann
2010-02-16 22:00 ` Nick Bowler
2010-02-16 22:18 ` Volker Armin Hemmann
2010-02-17 14:25 ` Nick Bowler
2010-02-18 9:27 ` Ian Dall
2010-02-17 1:03 ` Mr. James W. Laferriere
2010-02-17 2:01 ` Neil Brown
2010-02-17 2:38 ` Volker Armin Hemmann
2010-02-17 23:15 ` Neil Brown
2010-02-17 6:34 ` Kyle Moffett
2010-02-17 9:38 ` Rudy Zijlstra
2010-02-17 13:26 ` Frans Pop
2010-02-17 20:54 ` Gabor Gombas
2010-02-17 21:29 ` Frans Pop
2010-02-18 3:40 ` Goswin von Brederlow
2010-02-17 16:22 ` Kyle Moffett
2010-02-17 17:41 ` david
2010-02-17 18:10 ` Nick Bowler
2010-02-17 18:27 ` Volker Armin Hemmann
2010-02-17 18:37 ` Nick Bowler
2010-02-17 18:41 ` david
2010-02-17 18:51 ` Nick Bowler
2010-02-17 21:17 ` david
2010-02-17 21:37 ` Nick Bowler
2010-02-17 22:21 ` david
2010-02-17 18:46 ` Volker Armin Hemmann
2010-02-17 22:26 ` H. Peter Anvin
2010-02-18 3:33 ` Goswin von Brederlow
2010-02-18 7:51 ` Luca Berra
2010-02-18 14:12 ` Nick Bowler
2010-02-19 9:04 ` Michael Evans
2010-02-14 19:34 ` Henrique de Moraes Holschuh
2010-02-14 20:07 ` Michael Evans
2010-02-14 21:14 ` Henrique de Moraes Holschuh
2010-02-14 20:47 ` Asdo
2010-02-14 21:26 ` Henrique de Moraes Holschuh
2010-02-14 21:28 ` Gabor Gombas
2010-02-15 9:08 ` martin f krafft
2010-02-15 7:51 ` Luca Berra
[not found] <edBWa-K7-9@gated-at.bofh.it>
[not found] ` <edDXX-3XC-7@gated-at.bofh.it>
[not found] ` <edRHA-7bL-13@gated-at.bofh.it>
[not found] ` <eezfA-4N7-11@gated-at.bofh.it>
2010-02-16 21:10 ` Bodo Eggert
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=20100218101035.3a104fed@notabene.brown \
--to=neilb@suse.de \
--cc=giotex@texsoft.it \
--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).