Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
Date: Fri, 15 Mar 2013 12:10:35 +0600	[thread overview]
Message-ID: <20130315121035.68a7fae1@natsu> (raw)
In-Reply-To: <FCBB3555-81D9-4C7E-87D5-9AFBE20ED529@colorremedies.com>

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]

On Thu, 14 Mar 2013 21:43:14 -0600
Chris Murphy <lists@colorremedies.com> wrote:

> 
> On Mar 14, 2013, at 4:10 PM, Roman Mamedov <rm@romanrm.ru> wrote:
> > 
> > - shouldn't the reads have been quietly satisfied my md3 from sdf1, instead of just passing the buck^W error
> >  due to unreadable sdg1 to the higher (filesystem) layer?
> 
> What distro kernel and version?

Debian Testing, but I use vanilla 3.7.6 kernel, not distro's.

> Since you're not using btrfs raid1 there isn't a second copy maintained by btrfs itself, so it can't fix this. It's reporting a checksum failure for the single copy of data on the md raid1. It is getting the data elsewhere but it's btrfs saying that the checksum doesn't match.

So my guess (but that's already something like an accusation and not a founded
one at the moment :) that maybe mdadm failed to properly get data elsewhere,
and in case of errors it returned something like a zero-filled block, at which
btrfs correctly complained?..

Point is, I thought no user of md3 (be it btrfs or not) should have noticed any
errors "below" it, and in my case this turned out not to be the case.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-03-15  6:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 22:10 md RAID1 passes I/O errors to the filesystem despite having alive mirrors? Roman Mamedov
2013-03-15  3:43 ` Chris Murphy
2013-03-15  6:10   ` Roman Mamedov [this message]
2013-03-15  4:04 ` Chris Murphy
2013-03-15  6:02   ` Roman Mamedov
2013-03-15 11:07 ` Roy Sigurd Karlsbakk
2013-03-15 11:21   ` Roman Mamedov
2013-03-15 12:32     ` Roy Sigurd Karlsbakk
2013-03-15 16:19     ` Chris Murphy
2013-03-17 13:04       ` Roy Sigurd Karlsbakk
2013-03-17 18:22         ` Chris Murphy

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=20130315121035.68a7fae1@natsu \
    --to=rm@romanrm.ru \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@colorremedies.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