From: John Robinson <john.robinson@anonymous.org.uk>
To: "Timothy D. Lenz" <tlenz@vorgon.com>
Cc: "Mathias Burén" <mathias.buren@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: component device mismatches found: 9600
Date: Tue, 02 Aug 2011 01:35:33 +0100 [thread overview]
Message-ID: <4E374655.9040209@anonymous.org.uk> (raw)
In-Reply-To: <4E370227.2070804@vorgon.com>
On 01/08/2011 20:44, Timothy D. Lenz wrote:
> On 7/31/2011 11:32 AM, Mathias Burén wrote:
>> On 31 July 2011 19:24, Timothy D. Lenz<tlenz@vorgon.com> wrote:
>>> 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 01:03:01 x64VDR mdadm[2003]: RebuildFinished event detected on md
>>> device /dev/md1, component device mismatches found: 9600
[...]
> md1 : active raid1 sdb2[1] sda2[0]
> 4891712 blocks [2/2] [UU]
Hmm. Is this 5GB RAID-1 your swap partition? If so, don't worry about it
- there is an oddity that mismatches can crop up on RAID-1 arrays when a
write is abandoned after one drive has been written but the other hasn't
(I think that's the explanation), it's most often seen on swap, and it's
harmless.
Red Hat disabled reporting mismatches on RAID-1 because of this.
Cheers,
John.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-08-02 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 18:24 component device mismatches found: 9600 Timothy D. Lenz
2011-07-31 18:32 ` 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 [this message]
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=4E374655.9040209@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.com \
--cc=tlenz@vorgon.com \
/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 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).