linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux mdadm superblock question.
Date: Thu, 18 Feb 2010 10:11:54 +1100	[thread overview]
Message-ID: <20100218101154.5074ecdc@notabene.brown> (raw)
In-Reply-To: <alpine.DEB.2.00.1002160807370.31195@p34.internal.lan>

On Tue, 16 Feb 2010 08:14:21 -0500 (EST)
Justin Piszcz <jpiszcz@lucidpixels.com> wrote:

> 
> 
> On Tue, 16 Feb 2010, Neil Brown wrote:
> 
> > On Thu, 11 Feb 2010 18:00:23 -0500 (EST)
> > Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> >
> >> Hi,
> >>
> >> I may be converting a host to ext4 and was curious, is 0.90 still the only
> >> superblock version for mdadm/raid-1 that you can boot from without having
> >> to create an initrd/etc?
> >>
> >> Are there any benefits to using a superblock > 0.90 for a raid-1 boot
> >> volume < 2TB?
> >
> > The only noticeable differences that I can think of are:
> > 1/ If you reboot during recovery of a spare, then 0.90 will restart the
> >    recovery at the start, while 1.x will restart from where it was up to.
> > 2/ The /sys/class/block/mdXX/md/dev-YYY/errors counter is reset on each
> >    re-assembly with 0.90, but is preserved across stop/start with 1.x
> > 3/ If your partition starts on a multiple of 64K from the start of the
> >    device and is the last partition and contains 0.90 metadata, then
> >    mdadm can get confused by it.
> > 4/ If you move the devices to a host with a different arch and different
> >    byte-ordering, then extra effort will be needed to see the array for
> >    0.90, but not for 1.x
> >
> > I suspect none of these is a big issue.
> >
> > It is likely that future extensions will only be supported on 1.x metadata.
> > For example I hope to add support for storing a bad-block list, so that a
> > read error during recovery will only be fatal for that block, not the whole
> > recovery process.  This is unlikely ever to be supported on 0.90.  However
> > it may not be possible to hot-enable it on 1.x either, depending on how much
> > space has been reserved for extra metadata, so there is no guarantee that
> > using 1.x now makes you future-proof.
> >
> > And yes, 0.90 is still the only superblock version that supports in-kernel
> > autodetect, and I have no intention of adding in-kernel autodetect for any
> > other version.
> >
> > NeilBrown
> >
> 
> Hi Neil,
> 
> Thanks for the response, this is exactly what I was looking for and 
> probably should be put in a FAQ.
>
I believe the linux-raid wiki is open for anyone to update.  Feel free :-)

NeilBrown

  parent reply	other threads:[~2010-02-17 23:11 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
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     ` Neil Brown [this message]
2010-02-16 17:24   ` Linux mdadm superblock question 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=20100218101154.5074ecdc@notabene.brown \
    --to=neilb@suse.de \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.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).