From: NeilBrown <neilb@suse.de>
To: Phil Turmel <philip@turmel.org>
Cc: Fabian Knorr <knorrfab@fim.uni-passau.de>, linux-raid@vger.kernel.org
Subject: Re: Recovering an Array with inconsistent Superblocks
Date: Mon, 6 Jan 2014 10:50:11 +1100 [thread overview]
Message-ID: <20140106105011.3e58bbdc@notabene.brown> (raw)
In-Reply-To: <52C9A399.5040802@turmel.org>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
On Sun, 05 Jan 2014 13:25:29 -0500 Phil Turmel <philip@turmel.org> wrote:
> Hi Fabian,
>
> I see good news to greet me this morning!
>
> On 01/05/2014 05:45 AM, Fabian Knorr wrote:
> > $ cat /proc/mdstat
> > Personalities : [raid6] [raid5] [raid4]
> > md127 : active (auto-read-only) raid5 sde1[6] sdh1[2] sdi1[3] sdb1[4] sdg1[1] sdc1[5] sdf1[0]
> > 11721074688 blocks level 5, 1024k chunk, algorithm 2 [7/7] [UUUUUUU]
> > resync=PENDING
>
> Auto-read-only will switch to read-write as soon as you actually write
> anything to the array. Which will also kick off the resync.
You can also "mdadm --readwrite /dev/md127" to allow resync to continue.
> 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.
While I would encourage the use for 1.x metadata, you don't strictly need it
for a bitmap. 0.90 metadata supports bitmaps too, though it is slightly less
flexibly in the granularity of the bitmap (not that you would probably
notice).
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-01-05 23:50 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 [this message]
2014-01-06 14:00 ` Fabian Knorr
2014-01-07 0:26 ` NeilBrown
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=20140106105011.3e58bbdc@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).