From: Pavel Herrmann <morpheus.ibis@gmail.com>
To: Roman Mamedov <rm@romanrm.ru>
Cc: linux-raid@vger.kernel.org
Subject: Re: data corruption after rebuild
Date: Tue, 19 Jul 2011 18:35:26 +0200 [thread overview]
Message-ID: <4879002.CX4iSyfhxZ@bloomfield> (raw)
In-Reply-To: <20110719211240.2578bba6@natsu>
On Tuesday 19 of July 2011 21:12:40 Roman Mamedov wrote:
> > I do monthly scans, so the redundancy syndromes should have been
> > up-to-date, the array is made of 8 disks, the setup is ext4 on lvm on
> > mdraid
>
> Did you notice any nonzero mismatch_cnt during those scans?
oh crap, the rebuild finished with
Jul 19 09:41:24 Bloomfield mdadm[3996]: RebuildFinished event detected on md device /dev/md0, component device mismatches found: 3184
this is really bad i presume?
next prev parent reply other threads:[~2011-07-19 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 13:55 data corruption after rebuild Pavel Herrmann
2011-07-19 15:12 ` Roman Mamedov
2011-07-19 16:18 ` Pavel Herrmann
2011-07-19 17:38 ` Roman Mamedov
2011-07-19 17:44 ` Pavel Herrmann
2011-07-19 16:35 ` Pavel Herrmann [this message]
2011-07-19 16:48 ` Roman Mamedov
2011-07-19 17:05 ` Pavel Herrmann
2011-07-19 18:12 ` Roman Mamedov
2011-07-20 6:24 ` NeilBrown
2011-07-20 8:20 ` Pavel Herrmann
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=4879002.CX4iSyfhxZ@bloomfield \
--to=morpheus.ibis@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.ru \
/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).