From: Roman Mamedov <rm@romanrm.ru>
To: Pavel Herrmann <morpheus.ibis@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: data corruption after rebuild
Date: Tue, 19 Jul 2011 22:48:19 +0600 [thread overview]
Message-ID: <20110719224819.7aa5582d@natsu> (raw)
In-Reply-To: <4879002.CX4iSyfhxZ@bloomfield>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
On Tue, 19 Jul 2011 18:35:26 +0200
Pavel Herrmann <morpheus.ibis@gmail.com> wrote:
> 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?
Well, this basically tells you what you already know - a part of the data you have was corrupted. In this case I think it's 3184 512-byte sectors, which is about 1.6MB total.
How it got there and how to prevent that from happening in the future - that's a whole different question.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-07-19 16:48 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
2011-07-19 16:48 ` Roman Mamedov [this message]
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=20110719224819.7aa5582d@natsu \
--to=rm@romanrm.ru \
--cc=linux-raid@vger.kernel.org \
--cc=morpheus.ibis@gmail.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 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.