From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Clemens Eisserer <linuxhippy@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Can btrfs silently repair read-error in raid1
Date: Tue, 08 May 2012 09:26:53 +0200 [thread overview]
Message-ID: <4FA8CABD.5050006@jan-o-sch.net> (raw)
In-Reply-To: <CAFvQSYTtcxdy=y4LiV6x8znDm+UD-or1TFMvLrUbad6d+cXqbQ@mail.gmail.com>
On Tue, May 08, 2012 at 09:13 (+0200), Clemens Eisserer wrote:
> Would it be possible to create 2 btrfs partitions on that drive and
> use it in RAID1 - with btrfs silently repairing read-errors when they
> occur?
> Would it require special settings, to not fallback to read-only mode
> when a read-error occurs?
No special settings required, that's exactly what btrfs is doing by
default. Though, it's not completely silent: it will tell you in your
kernel log about the repair it did.
-Jan
next prev parent reply other threads:[~2012-05-08 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 7:13 Can btrfs silently repair read-error in raid1 Clemens Eisserer
2012-05-08 7:26 ` Jan Schmidt [this message]
2012-05-08 7:36 ` Fajar A. Nugraha
2012-05-08 10:45 ` cwillu
2012-05-08 21:47 ` Hubert Kario
2012-05-09 11:08 ` Atila
2012-05-08 23:34 ` Chris Samuel
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=4FA8CABD.5050006@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linuxhippy@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 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).