summaryrefslogtreecommitdiffstats
path: root/health/guides/mdstat/mdstat_mismatch_cnt.md
diff options
context:
space:
mode:
Diffstat (limited to 'health/guides/mdstat/mdstat_mismatch_cnt.md')
-rw-r--r--health/guides/mdstat/mdstat_mismatch_cnt.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/health/guides/mdstat/mdstat_mismatch_cnt.md b/health/guides/mdstat/mdstat_mismatch_cnt.md
new file mode 100644
index 000000000..7a156e38f
--- /dev/null
+++ b/health/guides/mdstat/mdstat_mismatch_cnt.md
@@ -0,0 +1,15 @@
+### Understand the alert
+
+This alert presents the number of unsynchronized blocks for the RAID array in crisis. Receiving this alert indicates a high number of unsynchronized blocks for the RAID array. This might indicate that data on the array is corrupted.
+
+This alert is raised to warning when the metric exceeds 1024 unsynchronized blocks.
+
+### Troubleshoot the alert
+
+There is no standard approach to troubleshooting this alert because the reasons can be various.
+
+For example, one of the reasons might be a swap on the array, which is relatively harmless. However, this alert can also be triggered by hardware issues which can lead to many problems and inconsistencies between the disks.
+
+### Useful resources
+
+[Serverfault | Reasons for high mismatch_cnt on a RAID1/10 array](https://serverfault.com/questions/885565/what-are-raid-1-10-mismatch-cnt-0-causes-except-for-swap-file/885574#885574)