From: NeilBrown <neilb@suse.de>
To: Fabian Knorr <knorrfab@fim.uni-passau.de>
Cc: Phil Turmel <philip@turmel.org>, linux-raid@vger.kernel.org
Subject: Re: Recovering an Array with inconsistent Superblocks
Date: Tue, 7 Jan 2014 11:26:27 +1100 [thread overview]
Message-ID: <20140107112627.32894e72@notabene.brown> (raw)
In-Reply-To: <1389016846.25272.5.camel@vessel>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
On Mon, 06 Jan 2014 15:00:46 +0100 Fabian Knorr <knorrfab@fim.uni-passau.de>
wrote:
> Many thanks to both of you, Phil and Neil!
>
> Everything works flawlessly now and I had no data loss whatsoever.
>
> > Long term, consider creating a new array with metadata type 1.x so you
> > can use a bitmap. If you ever have an event like this, where one or
> > more devices are disconnected then reconnected, it'll greatly shorten
> > the recovery time.
>
> But it's not possible to upgrade the metadata version of an existing
> array, is it?
With mdadm-3.3 you can assemble an array with 0.90 metadata using
mdadm --assemble --update=metadata /dev/mdWHATEVER /dev/.....
and it will be converted to 1.0 metadata.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-01-07 0:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 10:04 Recovering an Array with inconsistent Superblocks Fabian Knorr
2014-01-04 16:24 ` Phil Turmel
2014-01-04 17:59 ` Can Jeuleers
2014-01-04 19:16 ` Phil Turmel
2014-01-04 22:05 ` Fabian Knorr
2014-01-05 2:32 ` Phil Turmel
2014-01-05 9:07 ` Fabian Knorr
2014-01-05 9:56 ` NeilBrown
2014-01-05 10:40 ` Fabian Knorr
[not found] ` <1388918703.3591.20.camel@vessel>
2014-01-05 18:25 ` Phil Turmel
2014-01-05 23:50 ` NeilBrown
2014-01-06 14:00 ` Fabian Knorr
2014-01-07 0:26 ` NeilBrown [this message]
2014-01-14 8:54 ` David Brown
2014-01-04 22:08 ` Fabian Knorr
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=20140107112627.32894e72@notabene.brown \
--to=neilb@suse.de \
--cc=knorrfab@fim.uni-passau.de \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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).