From: Gareth Pye <gareth@cerberos.id.au>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Ulli Horlacher <framstag@rus.uni-stuttgart.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: RAID0 wrong (raw) device?
Date: Fri, 14 Aug 2015 08:32:46 +1000 [thread overview]
Message-ID: <CA+WRLO9ZbjZyNnMM951xrkE5OqymO3E8gMeebOpkX1a4qCS+6g@mail.gmail.com> (raw)
In-Reply-To: <55CC830D.2070304@gmail.com>
On Thu, Aug 13, 2015 at 9:44 PM, Austin S Hemmelgarn
<ahferroin7@gmail.com> wrote:
> 3. See the warnings about doing block level copies and LVM snapshots of
> BTRFS volumes, the same applies to using it on DRBD currently as well (with
> the possible exception of remote DRBD nodes (ie, ones without a local copy
> of the backing store) (in this case, we need to blacklist backing devices
> for stacked storage (I think the same issue may be present with BTRFS on a
> MD based RAID1 set).
I've been using BTRFS on top of DRBD for several years now, what
specifically am I meant to avoid?
I have 6 drives mirrored across a local network, this is done with DRBD.
At any one time only a single server has the 6 drives mounted with btrfs.
Is this a ticking time bomb?
--
Gareth Pye - blog.cerberos.id.au
Level 2 MTG Judge, Melbourne, Australia
"Dear God, I would like to file a bug report"
next prev parent reply other threads:[~2015-08-13 22:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 13:07 RAID0 wrong (raw) device? Ulli Horlacher
2015-08-12 17:03 ` Chris Murphy
2015-08-12 17:43 ` Hugo Mills
2015-08-12 17:53 ` Chris Murphy
2015-08-13 12:11 ` Ulli Horlacher
2015-08-13 7:34 ` anand jain
2015-08-13 12:02 ` Ulli Horlacher
2015-08-13 14:55 ` Ulli Horlacher
2015-08-13 16:24 ` Anand Jain
2015-08-14 7:32 ` Ulli Horlacher
2015-08-15 0:02 ` Anand Jain
2015-08-15 10:09 ` Ulli Horlacher
2015-08-13 11:44 ` Austin S Hemmelgarn
2015-08-13 12:06 ` Ulli Horlacher
2015-08-13 22:32 ` Gareth Pye [this message]
2015-08-13 22:54 ` Hugo Mills
2015-08-13 23:29 ` Gareth Pye
2015-08-14 11:26 ` Austin S Hemmelgarn
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=CA+WRLO9ZbjZyNnMM951xrkE5OqymO3E8gMeebOpkX1a4qCS+6g@mail.gmail.com \
--to=gareth@cerberos.id.au \
--cc=ahferroin7@gmail.com \
--cc=framstag@rus.uni-stuttgart.de \
--cc=linux-btrfs@vger.kernel.org \
/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).