I'm maintaining a pre-configured storage system for a project team. The storage consists of 36 x 8 TB HGST Disks (~240 TB net) in RAID60 (2x18 disks in RAID6), Controller is a MegaRAID SAS 9361-8i, OS=Scientific Linux 7.2
storcli64 /c0 /v1 show
DG/VD TYPE State Access Consist Cache Cac sCC Size Name
0/1 RAID60 Optl RW Yes RWBD - ON 232.860 TB
When running weekly scheduled consistency checks (or if I trigger them manually), I get a lot of inconsistency warnings, but they never seem to be fixed - during the next cc the same warnings reappear:
[root@faith ~]# grep 22649241 /var/log/message*
/var/log/messages:Oct 25 20:54:01 faith MR_MONITOR[1604]: <MRMON063> Controller ID: 0 Consistency Check found inconsistent parity on VD#012 strip: #012 ( VD = 1, strip#012 = 22649241)
/var/log/messages-20161002:Sep 25 22:34:03 faith MR_MONITOR[1604]: <MRMON063> Controller ID: 0 Consistency Check found inconsistent parity on VD#012 strip: #012 ( VD = 1, strip#012 = 22649241)
/var/log/messages-20161024:Oct 23 22:35:46 faith MR_MONITOR[1604]: <MRMON063> Controller ID: 0 Consistency Check found inconsistent parity on VD#012 strip: #012 ( VD = 1, strip#012 = 22649241)
What would be the best way to get array consistent? I guess a rebuild could likely fail in the current state? Or might this be a side effect of the raid60?
