From: Christoph Hellwig <hch@infradead.org>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>, 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: Fri, 3 Oct 2025 00:45:29 -0700 [thread overview]
Message-ID: <aN9_GeMp4jIlISuk@infradead.org> (raw)
In-Reply-To: <4ffbf6f3-1a6d-44fb-ad9b-df5f4cae79c1@gmail.com>
On Mon, Sep 29, 2025 at 09:34:32PM -0400, Demi Marie Obenour wrote:
> 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?
Well, if the file system is not mounted whoever pokes at it is obviously
in control. And needs full understanding of the on-disk structures.
next prev parent reply other threads:[~2025-10-03 7:45 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
2025-10-03 7:45 ` Christoph Hellwig [this message]
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=aN9_GeMp4jIlISuk@infradead.org \
--to=hch@infradead.org \
--cc=demiobenour@gmail.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).