From: Gionatan Danti <g.danti@assyoma.it>
To: NeilBrown <neilb@suse.de>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
linux-raid@vger.kernel.org, g.danti@assyoma.it
Subject: Re: On URE and RAID rebuild - again!
Date: Thu, 31 Jul 2014 09:16:24 +0200 [thread overview]
Message-ID: <53D9ED48.9000307@assyoma.it> (raw)
In-Reply-To: <20140731073121.38cd1773@notabene.brown>
> Yes, you can usually get your data back with mdadm.
>
> With latest code, a URE during recovery will cause a bad-block to be recorded
> on the recovered device, and recovery will continue. You end up with a
> working array that has a few unreadable blocks on it.
>
> NeilBrown
This is very good news :)
I case of parity RAID I assume the entire stripe is marked as bad, but
with mirror (eg: RAID10) only a single block (often 512B) is marked bad
on the recovered device, right?
From what mdadm/kernel version the new behavior is implemented? Maybe
the software RAID on my CentOS 6.5 is stronger then expected ;)
Regards.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2014-07-31 7:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 8:29 On URE and RAID rebuild - again! Gionatan Danti
2014-07-30 11:13 ` Mikael Abrahamsson
2014-07-30 13:05 ` Gionatan Danti
2014-07-30 21:31 ` NeilBrown
2014-07-31 7:16 ` Gionatan Danti [this message]
2014-08-02 16:21 ` Gionatan Danti
2014-08-03 3:48 ` NeilBrown
2014-08-04 7:02 ` Mikael Abrahamsson
2014-08-04 7:13 ` NeilBrown
2014-08-04 13:27 ` Gionatan Danti
2014-08-04 18:40 ` Mikael Abrahamsson
2014-08-04 22:44 ` Gionatan Danti
2014-08-04 23:29 ` NeilBrown
2014-08-05 6:52 ` Gionatan Danti
2014-08-05 19:01 ` Piergiorgio Sartor
2014-08-05 19:42 ` Gionatan Danti
2014-08-06 17:05 ` Chris Murphy
2014-08-06 16:34 ` Chris Murphy
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=53D9ED48.9000307@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=swmike@swm.pp.se \
/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).