From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: linux-raid@vger.kernel.org
Subject: component device mismatches found: 9600
Date: Sun, 31 Jul 2011 11:24:00 -0700 [thread overview]
Message-ID: <4E359DC0.5090608@vorgon.com> (raw)
Looking through the logs, I found this in daemon.log.0. Is this a sign
of a problem? Below is the entire log:
Jul 3 00:57:01 x64VDR mdadm[2003]: RebuildStarted event detected on md
device /dev/md0
Jul 3 00:57:02 x64VDR mdadm[2003]: RebuildStarted event detected on md
device /dev/md3
Jul 3 01:02:10 x64VDR mdadm[2003]: RebuildStarted event detected on md
device /dev/md1
Jul 3 01:02:10 x64VDR mdadm[2003]: RebuildFinished event detected on md
device /dev/md0
Jul 3 01:03:01 x64VDR mdadm[2003]: RebuildStarted event detected on md
device /dev/md2
Jul 3 01:03:01 x64VDR mdadm[2003]: RebuildFinished event detected on md
device /dev/md1, component device mismatches found: 9600
Jul 3 01:19:41 x64VDR mdadm[2003]: Rebuild29 event detected on md
device /dev/md3
Jul 3 01:19:41 x64VDR mdadm[2003]: Rebuild21 event detected on md
device /dev/md2
Jul 3 01:36:21 x64VDR mdadm[2003]: Rebuild50 event detected on md
device /dev/md3
Jul 3 01:36:21 x64VDR mdadm[2003]: Rebuild41 event detected on md
device /dev/md2
Jul 3 01:53:01 x64VDR mdadm[2003]: Rebuild67 event detected on md
device /dev/md3
Jul 3 02:09:41 x64VDR mdadm[2003]: Rebuild83 event detected on md
device /dev/md3
Jul 3 02:09:41 x64VDR mdadm[2003]: Rebuild75 event detected on md
device /dev/md2
Jul 3 02:26:21 x64VDR mdadm[2003]: Rebuild88 event detected on md
device /dev/md2
Jul 3 02:32:20 x64VDR mdadm[2003]: RebuildFinished event detected on md
device /dev/md3
Jul 3 02:43:23 x64VDR mdadm[2003]: RebuildFinished event detected on md
device /dev/md2
next reply other threads:[~2011-07-31 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 18:24 Timothy D. Lenz [this message]
2011-07-31 18:32 ` component device mismatches found: 9600 Mathias Burén
2011-08-01 19:44 ` Timothy D. Lenz
2011-08-01 19:49 ` Mathias Burén
2011-08-01 23:25 ` Timothy D. Lenz
2011-08-02 0:35 ` John Robinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E359DC0.5090608@vorgon.com \
--to=tlenz@vorgon.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.