Software Raid and mismatch_cnt

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

 



After the upgrade to CentOS 5.4, messages about mismatch_cnt != 0 started to annoy us every week.

Hours of reading, and performing some simple test didn't get us to the answer we need.

Does this mean that our files may be corrupted by these mismatches ?

Looks like this is true, for raid1 arrays.

Can you please confirm, or better disagree, if it's the case.

Thank you in advance for your attention, and time.
--
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