Re: Filesystem corruption on RAID1

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

 




Am 01.09.2017 um 00:55 schrieb Robert L Mathews:
On 8/20/17 3:43 AM, Mikael Abrahamsson wrote:

Indeed, but as far as I know there is nothing md can do about this. What
md could do about it is at least present a consistent view of data to
fsck (which for raid1 would be read all stripes and issue "repair" if
they don't match). Yes, this might indeed cause corruption but at least
it would be consistent and visible.

If you set all disks except one as "write-mostly", won't mdadm give you
a consistent view of it because it only reads from a single disk?

you gain nothing when you completly lie to fsck and after that switch back to normal operations with the other disks part of the game

and it works only on RAID1 and *really* RAID1, otherwise my current RAID10 would be as fast as hell instead the terrible random lags which are worser sometimes as before replace two out of 4 disks with a SSD
--
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