From: "Darrick J. Wong" <djwong@kernel.org>
To: Steve French <smfrench@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
samba-technical <samba-technical@lists.samba.org>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: misreported st_blocks (AllocationSize)
Date: Wed, 11 May 2022 13:20:22 -0700 [thread overview]
Message-ID: <20220511202022.GA1841530@magnolia> (raw)
In-Reply-To: <CAH2r5mvoQskGmY5SkgktzS1ZALeq7uk29EpLELLjVwcwYRwT1g@mail.gmail.com>
On Wed, May 11, 2022 at 02:33:01PM -0500, Steve French wrote:
> Was investigating trying to fix emulation of some fallocate flags, and
> was wondering how common is it for a fs to very loosely report
> allocation size (st_blocks) for a file - ie the allocation sizes does
> not match the allocate ranges returned by fiemap (or
> SEEK_HOLE/SEEK_DATA). Presumably there are Linux fs that coalesce
> ranges on the fly so allocation sizes may be a 'guess' for some fs.
>
> How common is this for it to be off?
Very common -- XFS reports /all/ file block usage in st_blocks,
including the extent mapping trees and staging areas for copy on write.
--D
> --
> Thanks,
>
> Steve
prev parent reply other threads:[~2022-05-11 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 19:33 misreported st_blocks (AllocationSize) Steve French
2022-05-11 20:20 ` Darrick J. Wong [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=20220511202022.GA1841530@magnolia \
--to=djwong@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@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;
as well as URLs for NNTP newsgroup(s).