From: Ethan Wilson <ethan.wilson@shiftmail.org>
To: linux-raid@vger.kernel.org
Subject: Re: Extremely High mismatch_cnt on RAID1 system
Date: Tue, 07 Oct 2014 15:14:22 +0200 [thread overview]
Message-ID: <5433E72E.60805@shiftmail.org> (raw)
In-Reply-To: <CAOWcSW5+8ZkWAyXL7VTk9JO+yrozFJS8RwroKqtudkiKD-fvXA@mail.gmail.com>
On 04/10/2014 15:46, Dennis Grant wrote:
> Hello all.
>
> ...
>
> Even after multiple checks, repairs, and rebuilds, the arrays on the
> bigger drives (/ and /home) are showing insanely high mismatch_cnt
> values. This has me concerned.
>
Dennis,
since nobody more knowledgeable replied, I will try.
Some mismatches on raid1 have been there since always, and nobody ever
deeply investigated what they were caused by, nor if they happen on
unallocated filesystem space or on real live data. It seems that if LVM
is between raid1 and the filesystem then they don't happen anymore, but
again nobody is really sure of why.
Recently some changes in the raid1 resync algorithm introduced some bugs
that could possibly generate additional mismatches, but if you haven't
had resyncs then I am not so sure if such bugs and their fixes are
relevant. However the fixes are here:
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.20
search for "raid".
You might want to upgrade to kernel 3.14.20, which is probably not what
your Ubuntu LTS has currently, then repair the arrays, then see if they
grow again.
Note that you need to do repair and not check:
echo repair > /sys/block/md0/md/sync_action
at the next "check" the mismatch_cnt should be 0 (not just after
"repair", because that would count the number of mismatches that have
been repaired).
I'd say that mismatches in general are pretty worrisome, they shouldn't
happen, they are likely to indicate corruption, so if what I said
doesn't work, e.g. mismatches grow again, try to report it again on the
list and somebody might be able to help further to track down this problem.
Regards
EW
next prev parent reply other threads:[~2014-10-07 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 13:46 Extremely High mismatch_cnt on RAID1 system Dennis Grant
2014-10-07 13:14 ` Ethan Wilson [this message]
2014-10-07 13:58 ` Wilson, Jonathan
2014-10-07 14:23 ` Ethan Wilson
2014-10-09 3:17 ` Brassow Jonathan
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=5433E72E.60805@shiftmail.org \
--to=ethan.wilson@shiftmail.org \
--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.