On Wed, 30 Jul 2014, Gionatan Danti wrote:
QUESTION n.1: Is this explanation correct?
QUESTION n.2: URE define a probability or a statistical evidence?
There has been much discussion about the URE figures. Some people
interpret it one way, others another way. There is nobody here that knows
for sure. Ask your HDD vendor, if they answer, do share here!
3) From what I understand having read some other mails, in the case of URE
during RAID rebuild mdadm will _stop_ the rebuild and inform you of what
happened. However, you could re-start the array, remount it and try to
recover data via normal filesystem copy. If, and when, the filesystem will
try to read the data affected by URE, mdadm will report back to it a "read
error" and the filesystem can react as it want (re-try the copy, report back
to user, abort the copy, etc.)
QUESTION n.3: is it what really happen on parity RAID (5,6)?
QUESTION n.4: what about mirror-striped array as RAID10? They follow the same
behavior?
When MD encounters an URE, it should calculate that block from parity
information and write it. I have personally had problems with this not
happening, seems it might be that if the URE doesn't happen repeatedly, MD
might not re-write. All parity raid levels should behave the same, so this
should work identically for RAID1, RAID10, RAID5 and RAID6.
--
Mikael Abrahamsson email: swmike@xxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
