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:02:57 +0600 [thread overview]
Message-ID: <20130315120257.60735a6f@natsu> (raw)
In-Reply-To: <E8003AD2-CDB8-4007-A80C-D95350144C90@colorremedies.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Thu, 14 Mar 2013 22:04:17 -0600
Chris Murphy <lists@colorremedies.com> wrote:
> 2. sdg is encountering UNC read errors, probably bad sectors, why it's new right?
It's not new, in fact it is in a questionable condition, but that's not the
issue I am looking for help with, in fact I am glad if me using this disk
suddenly helps uncover/solve some bug in mdadm :) I doubt it receives too much
testing with regard to its behavior in such rare circumstances (encountering
bad sectors on a member configured as write-mostly with btrfs on top of
everything, etc).
> 3. md3 might be getting the mirrored copy off sdf, I can't actually tell
>
> [ 771.438945] btrfs: bdev /dev/md3 errs: wr 0, rd 9, flush 0, corrupt 0, gen 0
>
> That line is btrfs reporting read errors from md3, not corruptions.
>
> [ 771.439011] ata11: EH complete
> [ 771.439035] btrfs no csum found for inode 31016 start 5668864
> [ 771.479594] btrfs csum failed ino 31016 off 5668864 csum 2731683453 private 0
>
> What are your btrfs mount options? Are you using nodatasum or nodatacow?
rw,noatime,nodiratime,compress=lzo,ssd,discard,space_cache,inode_cache
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-03-15 6:02 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
2013-03-15 4:04 ` Chris Murphy
2013-03-15 6:02 ` Roman Mamedov [this message]
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=20130315120257.60735a6f@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