From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>,
russell@coker.com.au, linux-btrfs@vger.kernel.org
Subject: Re: No space on empty, degraded raid10
Date: Thu, 11 Sep 2014 08:06:21 -0400 [thread overview]
Message-ID: <5411903D.4030801@gmail.com> (raw)
In-Reply-To: <20140911113833.GL5783@carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
On 2014-09-11 07:38, Hugo Mills wrote:
> On Thu, Sep 11, 2014 at 07:19:00AM -0400, Austin S Hemmelgarn wrote:
>> On 2014-09-11 02:40, Russell Coker wrote:
>>> Also it would be nice if there was a N-way mirror option for system data. As
>>> such data is tiny (32MB on the 120G filesystem in my workstation) the space
>>> used by having a copy on every disk in the array shouldn't matter.
>>
>> N-way mirroring is in the queue for after RAID5/6 work; ideally, once it
>> is ready, mkfs should default to one copy per disk in the filesystem.
>
> Why change the default from 2-copies, which it's been for years?
Sorry about the ambiguity in my statement, I meant that the default for
system chunks should be one copy per disk in the filesystem. If you
don't have a copy of the system chunks, then you essentially don't have
a filesystem, and that means that BTRFS RAID6 can't provide true
resilience against 2 disks failing catastrophically unless there are at
least 3 copies of the system chunks.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]
next prev parent reply other threads:[~2014-09-11 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 20:38 No space on empty, degraded raid10 Or Tal
2014-09-08 11:01 ` Austin S Hemmelgarn
2014-09-11 6:40 ` Russell Coker
2014-09-11 11:19 ` Austin S Hemmelgarn
2014-09-11 11:38 ` Hugo Mills
2014-09-11 12:06 ` Austin S Hemmelgarn [this message]
2014-09-11 12:10 ` Hugo Mills
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=5411903D.4030801@gmail.com \
--to=ahferroin7@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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).