From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: John Petrini <jpetrini@coredial.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Volume appears full but TB's of space available
Date: Fri, 7 Apr 2017 13:04:41 -0400 [thread overview]
Message-ID: <3ae6ec4c-fd30-66ab-2976-a9aa03e4dd22@gmail.com> (raw)
In-Reply-To: <CAD4AmV6yD4s09H4q2QEyjb=pPRkGoESgNv1dEfNCpYWAWcAsqQ@mail.gmail.com>
On 2017-04-07 12:58, John Petrini wrote:
> When you say "running BTRFS raid1 on top of LVM RAID0 volumes" do you
> mean creating two LVM RAID-0 volumes and then putting BTRFS RAID1 on
> the two resulting logical volumes?
Yes, although it doesn't have to be LVM, it could just as easily be MD
or even hardware RAID (I just prefer LVM for the flexibility it offers).
A quick tip regarding this, it seems to get the best performance if the
stripe size (the -I option for lvcreate) is chosen so that it either
matches the BTRFS block size, or such that each block in BTRFS gets
striped across all the disks.
next prev parent reply other threads:[~2017-04-07 17:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 0:47 Volume appears full but TB's of space available John Petrini
2017-04-07 1:15 ` John Petrini
2017-04-07 1:21 ` Chris Murphy
2017-04-07 1:31 ` John Petrini
2017-04-07 2:42 ` Chris Murphy
2017-04-07 3:25 ` John Petrini
2017-04-07 11:41 ` Austin S. Hemmelgarn
2017-04-07 13:28 ` John Petrini
2017-04-07 13:50 ` Austin S. Hemmelgarn
2017-04-07 16:28 ` Chris Murphy
2017-04-07 16:58 ` Austin S. Hemmelgarn
2017-04-07 17:05 ` John Petrini
2017-04-07 17:11 ` Austin S. Hemmelgarn
2017-04-07 16:04 ` Chris Murphy
2017-04-07 16:51 ` Austin S. Hemmelgarn
2017-04-07 16:58 ` John Petrini
2017-04-07 17:04 ` Austin S. Hemmelgarn [this message]
2017-04-08 5:12 ` Duncan
2017-04-10 11:31 ` Austin S. Hemmelgarn
2017-04-07 1:17 ` 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=3ae6ec4c-fd30-66ab-2976-a9aa03e4dd22@gmail.com \
--to=ahferroin7@gmail.com \
--cc=jpetrini@coredial.com \
--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;
as well as URLs for NNTP newsgroup(s).