Re: WARNING: mismatch_cnt is not 0 on <array device>

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

 



On 27/09/16 18:30, Benjammin2068 wrote:
> I have smartctl running for all my drives -- but that doesn't help me at the mdadm level.
> 
> While you're in the docs adding stuff about mismatch_cnt, is there anything that can help someone backtrace which block cause the count to go up? This would help us mere mortals maybe go back to inspect a block or a file or something to make sure it's not corrupted.

I'm planning to go back through the archives as best I can (I keep a
local archive :-), and I'm starring everything of interest. So if
anybody can chime in, I'll make a note! :-)

All this should eventually get there ... and I'm planning to add a
kernel programming section too - not least because I want to do some!

Cheers,
Wol
--
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