Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Chris Murphy <lists@colorremedies.com>,
	"linux-btrfs" <linux-btrfs@vger.kernel.org>
Subject: Re: RAID1: system stability
Date: Wed, 22 Jul 2015 21:00:22 +1000	[thread overview]
Message-ID: <201507222100.22471.russell@coker.com.au> (raw)
In-Reply-To: <CAJCQCtTXiWWie+OtkdNhjmUEjPoyx565LZ15KC3Kfr7DC9ucpQ@mail.gmail.com>

On Tue, 23 Jun 2015 02:52:43 AM Chris Murphy wrote:
> OK I actually don't know what the intended block layer behavior is
> when unplugging a device, if it is supposed to vanish, or change state
> somehow so that thing that depend on it can know it's "missing" or
> what. So the question here is, is this working as intended? If the
> layer Btrfs depends on isn't working as intended, then Btrfs is
> probably going to do wild and crazy things. And I don't know that the
> part of the block layer Btrfs depends on for this is the same (or
> different) as what the md driver depends on.

I disagree with that statement.  BTRFS should be expected to not do wild and 
crazy things regardless of what happens with block devices.

A BTRFS RAID-1/5/6 array should cope with a single disk failing or returning 
any manner of corrupted data and should not lose data or panic the kernel.

A BTRFS RAID-0 or single disk setup should cope with a disk giving errors by 
mounting read-only or failing all operations on the filesystem.  It should not 
affect any other filesystem or have any significant impact on the system unless 
it's the root filesystem.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/

  reply	other threads:[~2015-07-22 11:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 11:23 RAID1: system stability Timofey Titovets
2015-05-26 19:31 ` Timofey Titovets
2015-05-26 19:49 ` Chris Murphy
2015-05-26 19:51   ` Timofey Titovets
2015-06-22 11:35     ` Timofey Titovets
2015-06-22 11:45       ` Timofey Titovets
2015-06-22 16:03       ` Chris Murphy
2015-06-22 16:36         ` Timofey Titovets
2015-06-22 16:52           ` Chris Murphy
2015-07-22 11:00             ` Russell Coker [this message]
2015-08-05 17:32               ` Austin S Hemmelgarn
2015-08-05 19:00                 ` Martin Steigerwald
  -- strict thread matches above, loose matches on Subject: below --
2015-06-17  9:20 Timofey Titovets

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=201507222100.22471.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=linux-btrfs@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