From: Gionatan Danti <g.danti@assyoma.it>
To: Chris Murphy <lists@colorremedies.com>,
xfs list <linux-xfs@vger.kernel.org>
Cc: "'g.danti@assyoma.it'" <g.danti@assyoma.it>
Subject: Re: XFS reflink vs ThinLVM
Date: Mon, 13 Jan 2020 17:25:48 +0100 [thread overview]
Message-ID: <6882c726-2ac0-2d1e-155f-6e9a65009a45@assyoma.it> (raw)
In-Reply-To: <CAJCQCtShw=TTqfnxWpEROXfUgs2TtAOnLzPdi4LpOo9aYsN-gg@mail.gmail.com>
On 13/01/20 17:14, Chris Murphy wrote:
> Is --reflink on XFS atomic? In particular for a VM file that's being
> used, that's possibly quite a lot of metadata on disk and in-flight in
> the host and in the guest.
>
> I ask because I'm not certain --reflink copies on Btrfs are atomic,
> I'll have to ask over there too. Whereas btrfs subvolume snapshots are
> considered atomic.
Hi, I did that question some time ago and, based on what I read here
[1], it *should* be atomic.
Feel free to correct me, anyway.
[1] https://www.spinics.net/lists/linux-xfs/msg15969.html
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
prev parent reply other threads:[~2020-01-13 16:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 10:22 XFS reflink vs ThinLVM Gionatan Danti
2020-01-13 11:10 ` Carlos Maiolino
2020-01-13 11:25 ` Gionatan Danti
2020-01-13 11:43 ` Carlos Maiolino
2020-01-13 12:21 ` Gionatan Danti
2020-01-13 15:34 ` Gionatan Danti
2020-01-13 16:53 ` Darrick J. Wong
2020-01-13 17:00 ` Gionatan Danti
2020-01-13 18:09 ` Darrick J. Wong
2020-01-14 8:45 ` Gionatan Danti
2020-01-15 11:37 ` Gionatan Danti
2020-01-15 16:39 ` Darrick J. Wong
2020-01-15 17:45 ` Gionatan Danti
2020-01-17 21:58 ` Gionatan Danti
2020-01-17 23:42 ` Darrick J. Wong
2020-01-18 11:08 ` Gionatan Danti
2020-01-18 23:06 ` Darrick J. Wong
2020-01-19 8:45 ` Gionatan Danti
2020-01-13 16:14 ` Chris Murphy
2020-01-13 16:25 ` Gionatan Danti [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=6882c726-2ac0-2d1e-155f-6e9a65009a45@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.