From: Remi Gauvin <remi@georgianit.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: BTRFS and databases
Date: Thu, 2 Aug 2018 08:32:11 -0400 [thread overview]
Message-ID: <72a43ca7-bba5-2ecd-c33e-412a1b258e6f@georgianit.com> (raw)
In-Reply-To: <46d12c3f-9756-99be-a99c-75af5acc3296@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 741 bytes --]
On 2018-08-02 03:07 AM, Qu Wenruo wrote:
> For data, since we have cow (along with csum), it should be no problem
> to recover.
>
> And since datacow is used, transaction on each device should be atomic,
> thus we should be able to handle one-time device out-of-sync case.
> (For multiple out-of-sync events, we don't have any good way though).
>
> Or did I miss something from previous discussion?
As far as I know, that is indeed correct and works very well. The
question was specifically about using nodatacow for databases,, and
that's the question I was responding too. In the current state, I do no
believe btrfs nodatacow is in any way appropriate for databases/vm
hosting when combined with multi-device.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2018-08-02 14:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 3:45 BTRFS and databases MegaBrutal
2018-08-01 8:48 ` Duncan
2018-08-01 8:56 ` Hugo Mills
2018-08-02 9:16 ` Martin Steigerwald
2018-08-02 10:15 ` ein
2018-08-02 10:35 ` Andrei Borzenkov
2018-08-02 10:42 ` Martin Steigerwald
2018-08-02 10:53 ` Qu Wenruo
2018-08-01 8:59 ` Mike Fleetwood
2018-08-01 11:21 ` Adam Borowski
2018-08-01 12:19 ` Austin S. Hemmelgarn
2018-08-01 14:33 ` Remi Gauvin
2018-08-02 7:07 ` Qu Wenruo
2018-08-02 12:32 ` Remi Gauvin [this message]
2018-08-02 7:02 ` Qu Wenruo
2018-08-02 10:45 ` Andrei Borzenkov
2018-08-02 10:56 ` Qu Wenruo
2018-08-02 12:27 ` Austin S. Hemmelgarn
2018-08-02 13:14 ` Martin Raiber
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=72a43ca7-bba5-2ecd-c33e-412a1b258e6f@georgianit.com \
--to=remi@georgianit.com \
--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).