linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 19:05:39 +0200	[thread overview]
Message-ID: <2015932.L0f6vYYk3Y@bloomfield> (raw)
In-Reply-To: <20110719224819.7aa5582d@natsu>

On Tuesday 19 of July 2011 22:48:19 Roman Mamedov wrote:
> On Tue, 19 Jul 2011 18:35:26 +0200
> 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.

the number seems too low to me, I have about 2000 video files larger than 1GB 
on that array, and every one i tried has been corrupted enough to create 
almost unstoppable visual artifacts in hi-def video.


> How it got there and how to prevent that from
> happening in the future - that's a whole different question.

would ZFS in raidz2 mode be much better than raid6+ext4? I understand its not 
the topic of this list, but file-level checksummed rebuild looks like a nice 
feature



  reply	other threads:[~2011-07-19 17:05 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
2011-07-19 17:05       ` Pavel Herrmann [this message]
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=2015932.L0f6vYYk3Y@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).