Re: Revisit Old Issue - Raid1 (harmless still?) mismatch_cnt = 128 on scrub?

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

 





Am 03.12.22 um 10:41 schrieb David C. Rankin:
On 12/2/22 16:07, Reindl Harald wrote:


Am 02.12.22 um 22:49 schrieb David C. Rankin:
All,

   I have a Raid1 array on boot that showed 0 mismatch count for a couple of years, but lately shows:

mismatch_cnt = 128

sadly that's normal while i count it as a bug in mdadm

it depends more or less on random IO due raid-check and makes no sense at all (besides it's non-fixable anyways for a mirrored array because only god could know the truth)

Alas,

It's kind of a "phase of the moon thing" as far as I understand it for Raid1.

it's the same for RAID10 any it's idiotic to display that nonsense at all when it don't say anything useful

it has to be either fixed or removed after more than 10 years for the sake of god



[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