From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Gareth Pye <gareth@cerberos.id.au>,
Hugo Mills <hugo@carfax.org.uk>,
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 07:26:54 -0400 [thread overview]
Message-ID: <55CDD07E.9090708@gmail.com> (raw)
In-Reply-To: <CA+WRLO9ub4gX1Rj9+f1APNujL7zk_p7NApUUS-ExkfbuPjMQDQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On 2015-08-13 19:29, Gareth Pye wrote:
> I would have been surprised if any generic file system copes well with
> being mounted in several locations at once, DRBD appears to fight
> really hard to avoid that happening :)
>
> And yeah I'm doing the second thing, I've successfully switched which
> of the servers is active a few times with no ill effect (I would
> expect scrub to give me some significant warnings if one of the disks
> was a couple of months out of date) so I'm presuming that DRBD copes
> reasonably well or I've been very lucky. Either that luck is very
> deterministic, DRBD copes correctly, or I've been very very lucky.
>
> Very very lucky doesn't sound likely.
>
Yeah, I'd be willing to bet that DRBD does cope well with direct writes
to the backing store (either that or it prevents the kernel from doing
that, which would be even better and would not surprise me at all). In
my experience it's one of the most resilient shared storage options out
there.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
prev parent reply other threads:[~2015-08-14 11:27 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
2015-08-13 22:54 ` Hugo Mills
2015-08-13 23:29 ` Gareth Pye
2015-08-14 11:26 ` Austin S Hemmelgarn [this message]
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=55CDD07E.9090708@gmail.com \
--to=ahferroin7@gmail.com \
--cc=framstag@rus.uni-stuttgart.de \
--cc=gareth@cerberos.id.au \
--cc=hugo@carfax.org.uk \
--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).