From: Neil Brown <neilb@suse.de>
To: Matthias Urlichs <matthias@urlichs.de>
Cc: Doug Ledford <dledford@redhat.com>, linux-raid@vger.kernel.org
Subject: Re: RAID1 assembled broken array
Date: Fri, 25 Sep 2009 18:07:44 +1000 [thread overview]
Message-ID: <19132.31312.353493.453529@notabene.brown> (raw)
In-Reply-To: message from Matthias Urlichs on Thursday September 17
On Thursday September 17, matthias@urlichs.de wrote:
> On Thu, 2009-09-17 at 12:44 -0400, Doug Ledford wrote:
> > >> 1.0 also protects from this problem.
> > >
> > > So what's the best way to update a 0.9 superblock to 1.0 format?
> > >
> > > mdadm --assemble --metadata=1.0 --update=summaries ... ?
> >
> > I don't think you can. You just have to create a new array with the
> > new superblock.
> >
> Hmm. Looks like you're right.
>
> Consider this to be a feature request, then. If 1.0 is more reasonable
> than 0.9, there should be a "safe" upgrade path.
Yes, definitely. There should be.
Now if only there were more hours in the day.... :-)
NeilBrown
next prev parent reply other threads:[~2009-09-25 8:07 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 [this message]
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
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=19132.31312.353493.453529@notabene.brown \
--to=neilb@suse.de \
--cc=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=matthias@urlichs.de \
/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).