From: Christoph Hellwig <hch@infradead.org>
To: Priya PM <pmpriya@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Query: XFS reflink unique block measurement / snapshot accounting
Date: Sun, 13 Jul 2025 22:58:04 -0700 [thread overview]
Message-ID: <aHScbEVwQad_ryX5@infradead.org> (raw)
In-Reply-To: <CAP=9937nv-k1dTbHHRZF3=jizvRKcQNAa9_nM_Z1RA8VMYhKSg@mail.gmail.com>
On Sat, Jul 12, 2025 at 01:19:19PM +0530, Priya PM wrote:
> Hi,
>
> I was using reflinks to create snapshots of an XFS filesystem;
> however, I’m looking for ways to determine the unique snapshot usage
> or perform snapshot accounting.
Can you explain what you are trying to measure? How many blocks in a
given file are refcounted blocks with other users? Or the difference
between i_blocks for all files combined vs actual space usage?
There isn't really such a thing as snapshot accouting in XFS.
next prev parent reply other threads:[~2025-07-14 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-12 7:49 Query: XFS reflink unique block measurement / snapshot accounting Priya PM
2025-07-14 5:58 ` Christoph Hellwig [this message]
2025-07-15 13:51 ` Priya PM
2025-07-15 16:09 ` Christoph Hellwig
2025-07-14 20:54 ` Dave Chinner
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=aHScbEVwQad_ryX5@infradead.org \
--to=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pmpriya@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox