From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Ulli Horlacher <framstag@rus.uni-stuttgart.de>,
linux-btrfs@vger.kernel.org
Subject: Re: RAID0 wrong (raw) device?
Date: Thu, 13 Aug 2015 07:44:13 -0400 [thread overview]
Message-ID: <55CC830D.2070304@gmail.com> (raw)
In-Reply-To: <20150812130758.GA26529@rus.uni-stuttgart.de>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
A couple of observations:
1. BTRFS currently has no knowledge of multipath or anything like that.
In theory it should work fine as long as the multiple device instances
all point to the same storage directly (including having identical block
addresses), but we still need to add proper handling for it.
2. Be _VERY_ careful using BTRFS on top of _ANY_ kind of shared storage.
Most non-clustered filesystems will have issues if multiply mounted,
but in almost all cases I've personally seen, it _WILL_ cause
irreparable damage to a BTRFS filesystem (we really need to do something
like ext4's MMP in BTRFS).
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).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-08-13 11:44 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 [this message]
2015-08-13 12:06 ` Ulli Horlacher
2015-08-13 22:32 ` Gareth Pye
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=55CC830D.2070304@gmail.com \
--to=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).