From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Brian B <brian@sd85.net>,
Robert Krig <robert.krig@render-wahnsinn.de>,
Hans van Kranenburg <hans.van.kranenburg@mendix.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Need some help: "BTRFS critical (device sda): corrupt leaf, slot offset bad: block"
Date: Tue, 4 Apr 2017 09:52:12 -0400 [thread overview]
Message-ID: <b6524e54-1b36-bfb5-4137-b755acb9e985@gmail.com> (raw)
In-Reply-To: <0eda9836-a4ee-b666-2a05-b4bb26746b1a@sd85.net>
On 2017-04-04 09:29, Brian B wrote:
> On 04/04/2017 12:02 AM, Robert Krig wrote:
>> My storage array is BTRFS Raid1 with 4x8TB Drives.
>> Wouldn't it be possible to simply disconnect two of those drives, mount
>> with -o degraded and still have access (even if read-only) to all my data?
> Just jumping on this point: my understanding of BTRFS "RAID1" is that
> each file (block?) is randomly assigned to two disks of the array (no
> matter how many disks are in the array). So if you remove two disks,
> you will probably have files that were "assigned" to both of those
> disks, and will be missing.
>
> In short, you can't remove more than one disk of a BTRFS RAID1 and still
> have all of your data.
>
That understanding is correct. From a functional perspective, BTRFS
raid1 is currently a RAID10 implementation with striping happening at a
very large granularity.
next prev parent reply other threads:[~2017-04-04 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 10:11 Need some help: "BTRFS critical (device sda): corrupt leaf, slot offset bad: block" Robert Krig
2017-04-03 13:50 ` Robert Krig
2017-04-03 14:09 ` Hans van Kranenburg
2017-04-03 14:08 ` Hans van Kranenburg
2017-04-03 14:20 ` Robert Krig
2017-04-03 14:25 ` Robert Krig
2017-04-04 4:02 ` Robert Krig
2017-04-04 13:29 ` Brian B
2017-04-04 13:48 ` Hugo Mills
2017-04-04 13:52 ` Austin S. Hemmelgarn [this message]
2017-04-04 16:52 ` Chris Murphy
2017-04-04 16:55 ` Chris Murphy
2017-04-05 6:07 ` Robert Krig
2017-04-03 14:44 ` Hans van Kranenburg
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=b6524e54-1b36-bfb5-4137-b755acb9e985@gmail.com \
--to=ahferroin7@gmail.com \
--cc=brian@sd85.net \
--cc=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=robert.krig@render-wahnsinn.de \
/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).