summaryrefslogtreecommitdiffstats
path: root/health/guides/mdstat/mdstat_mismatch_cnt.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-03-09 13:19:22 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-03-09 13:19:22 +0000
commitc21c3b0befeb46a51b6bf3758ffa30813bea0ff0 (patch)
tree9754ff1ca740f6346cf8483ec915d4054bc5da2d /health/guides/mdstat/mdstat_mismatch_cnt.md
parentAdding upstream version 1.43.2. (diff)
downloadnetdata-upstream/1.44.3.tar.xz
netdata-upstream/1.44.3.zip
Adding upstream version 1.44.3.upstream/1.44.3
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
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)