From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
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: Sun, 17 Mar 2013 14:04:50 +0100 (CET) [thread overview]
Message-ID: <1567316.0.1363525490131.JavaMail.root@zimbra> (raw)
In-Reply-To: <E1F75819-ABCB-4C6F-85F4-1B812B168DB6@colorremedies.com>
> > This is correct, but I should note that I did not add it as
> > write-mostly just
> > because it's an older drive, but because it is my normal set-up for
> > md3:
> > a RAID1 mirror of a fast SSD (sdf) and a write-mostly HDD (sdg in
> > this case).
>
> Again, I find it odd that sdg while rebuilding is reading any sectors.
> The read errors are coming from sdg. That it's also write-mostly
> enhances the mystery why sdg is being read from.
>
> I would fail the HDD, and btrfs scrub the array which in effect should
> scrub only sdf. And it may also need an offline btrfsck. The source
> (sdf) is already suspect because of btrfs not finding checksums where
> it was expecting to find them, and then on top of this you're getting
> sdg producing bad sector errors on reads.
Have you done a SMART check of sdg? smartctl -H first, then smartctl -t short, then smartctl -t long (with smartctl -H between them)
> You might also consider posting the configuration and full dmesg to
> the btrfs list. I'm curious what btrfs developers think of this
> configuration.
It's not btrfs - it's below that.
Vennlige hilsener / Best regards
roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy@karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-03-17 13:04 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
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 [this message]
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=1567316.0.1363525490131.JavaMail.root@zimbra \
--to=roy@karlsbakk.net \
--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 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.