Re: mismatch sector in range, kernel 4.13

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Sep 09, 2017 at 07:26:51PM +0100, Anthony Youngman wrote:
> But with raid 5 you can only solve for a missing/corrupt block IF you can
> tell the system which one is messed up. Btrfs is telling you that the data
> is fine, so you know it's the parity, and raid 5 can fix that for you.

Thanks for confirming my understanding. I just wasn't 100% sure if md
now had extra checksums that would not allow you to reconstruct corrupt
data but would tell you which block was corrupted (i.e. not like parity
where you can actually rebuild, but enough to say "yes, this one doesn't
add up").

Anyway, I'm going to start a repair, thanks.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901
--
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



[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux