From: Demi Marie Obenour <demiobenour@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Can the output of FIEMAP on BTRFS be used to check if a file and its reflink copy might have diverged?
Date: Mon, 29 Sep 2025 21:34:32 -0400 [thread overview]
Message-ID: <4ffbf6f3-1a6d-44fb-ad9b-df5f4cae79c1@gmail.com> (raw)
In-Reply-To: <aNpIZ2iMChSUzD3y@infradead.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 900 bytes --]
On 9/29/25 04:50, Christoph Hellwig wrote:
> On Mon, Sep 22, 2025 at 01:54:56PM -0400, Demi Marie Obenour wrote:
>> This leaves the question of whether the needed information is in the
>> filesystem metadata. If so, xfsprogs and/or btrfsprogs could obtain
>> it from a block-layer snapshot offline without needing kernel changes.
>> Otherwise, kernel changes will be needed. I don't know if the changes
>> to the userspace tools will be accepted, though. Until then, btrfs
>> send/receive will be the only way to efficiently back up a BTRFS
>> filesystem, and XFS will only be able to be efficiently backed up
>> at the block level.
>
> Using userspace tools that poke at the block-level mapping is
> fundamentally unsafe because it is not synchronized with the file
> system.
Is it unsafe even if the filesystem is not mounted?
--
Sincerely,
Demi Marie Obenour (she/her/hers)
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-30 1:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 0:07 Can the output of FIEMAP on BTRFS be used to check if a file and its reflink copy might have diverged? Demi Marie Obenour
2025-09-22 0:50 ` Qu Wenruo
2025-09-22 18:24 ` Demi Marie Obenour
2025-09-22 21:38 ` Qu Wenruo
2025-09-22 16:48 ` Christoph Hellwig
2025-09-22 17:18 ` Demi Marie Obenour
2025-09-22 17:20 ` Christoph Hellwig
2025-09-22 17:30 ` Demi Marie Obenour
2025-09-22 17:31 ` Christoph Hellwig
2025-09-22 17:54 ` Demi Marie Obenour
2025-09-29 8:50 ` Christoph Hellwig
2025-09-29 23:56 ` Demi Marie Obenour
2025-09-30 1:34 ` Demi Marie Obenour [this message]
2025-10-03 7:45 ` Christoph Hellwig
2025-09-22 23:25 ` Chris Laprise
2025-09-29 8:49 ` Christoph Hellwig
2025-09-29 23:55 ` Demi Marie Obenour
2025-10-03 7:44 ` Christoph Hellwig
2025-10-04 1:09 ` Demi Marie Obenour
2025-10-04 1:43 ` Chris Laprise
2025-10-04 4:51 ` Christoph Hellwig
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=4ffbf6f3-1a6d-44fb-ad9b-df5f4cae79c1@gmail.com \
--to=demiobenour@gmail.com \
--cc=hch@infradead.org \
--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).