On 09/28/2016 10:55 AM, Benjammin2068 wrote: > On 09/27/2016 06:09 PM, Adam Goryachev wrote: >> Just out of interest, but I'm not sure how useful your munin monitoring will be... AFAIK, the mismatch_cnt value is only updated when you run a check, which would probably take some number of hours to complete. I would guess that you are unlikely to run more than one check a week or month.... and as soon as there is any change (unless you know the explanation) then you should be looking to resolve that. >> >> Unless of course I'm wrong about when the count is updated? > You would be correct - only during checks - but it's an easy way for me to just keep track of it.. > > And a check takes about 3hrs on this array. (and it happens every weekend) > > Ok... so as an update.... I ran 2 checks during the week after fixing the thermal issues I was seeing that I think were part of the problem. Both checks resulted in the mismatch_cnt remaining at 0. The usual CRON automated check ran this weekend -- and bumped the count to 24 on my RAID6 (there's a RAID1 swap that went to 160, but I've read for something like SWAP, this can be ignored. I just thought I'd mention it since it feels a bit like Schrodinger's drive array.) So... I've emailed the Vendor for a replacement since this SAS/SATA add-on card is new. And maybe it's just flaky. IN the meantime, is it possible to shrink the array back to RAID5 (4 members) so I can run it on the MB's controller only -- where I never seemed to have a mismatch count problem? (I kind need the array to be up and running since I need to work. :P) Also -- for academic reasons, is it possible to get a list of the the blocks that causes the count to increase to try confirm it's the new add-on card that's the problem? If there's a way to list what blocks and drive that were the issue, then I could go check those files.... Otherwise, the mdadm reports the array as clean and happy and FSCK reports the partition as clean and happy. How disconcerting is that? Thanks, -Ben -- 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
