linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* component device mismatches found
@ 2017-03-19 10:00 Gandalf Corvotempesta
  2017-03-19 10:21 ` Wols Lists
  0 siblings, 1 reply; 3+ messages in thread
From: Gandalf Corvotempesta @ 2017-03-19 10:00 UTC (permalink / raw)
  To: linux-raid

I've seen this in my log:

Mar 19 00:57:01 x /USR/SBIN/CRON[17832]: (root) CMD (if [ -x
/usr/share/mdadm/checkarray ]; then /usr/share/mdadm/checkarray --cron
--all --idle --quiet; fi)
Mar 19 00:57:01 x mdadm[1576]: RebuildStarted event detected on md
device /dev/md/0
Mar 19 01:30:21 x mdadm[1576]: Rebuild24 event detected on md device /dev/md/0
Mar 19 02:03:41 x mdadm[1576]: Rebuild47 event detected on md device /dev/md/0
Mar 19 02:37:02 x mdadm[1576]: Rebuild68 event detected on md device /dev/md/0
Mar 19 03:10:22 x mdadm[1576]: Rebuild87 event detected on md device /dev/md/0
Mar 19 03:38:00 x mdadm[1576]: RebuildFinished event detected on md
device /dev/md/0, component device  mismatches found: 4608

This is a 3way mirror.

I've tought that swap was the culpit, but swap isn't used:

# free -m
             total       used       free     shared    buffers     cached
Mem:         32230      31844        386          0       1679      26026
-/+ buffers/cache:       4137      28092
Swap:         8191          0       8191

and IIRC, linux never clean the swap usage up to 0.

Are my data safe ? Is something to be worried about ?

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-03-19 10:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-19 10:00 component device mismatches found Gandalf Corvotempesta
2017-03-19 10:21 ` Wols Lists
     [not found]   ` <CAJH6TXhYYuh3v8FDDUisCpTZqVJ3WHEb_W0Ky=jkQHm1Y-fR4w@mail.gmail.com>
2017-03-19 10:42     ` Fwd: " Gandalf Corvotempesta

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).