From: Benjamin Coddington <bcodding@redhat.com>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Async client v4 mount results in unexpected number of extents on the server
Date: Fri, 11 Apr 2025 09:29:29 -0400 [thread overview]
Message-ID: <3696A877-3C0E-4F70-9C7E-3FD8B9AD185F@redhat.com> (raw)
In-Reply-To: <848f71b0-7e27-fce1-5e43-2d3c8d4522b4@applied-asynchrony.com>
On 10 Apr 2025, at 8:55, Holger Hoffstätte wrote:
> ...
> Does this behaviour seem familiar to anybody?
>
> I realize this is "not a bug" (all data is safe and sound etc.) but
> somehow it seems that various layers are not working together as one
> might expect. It's possible that my expectation is wrong. :)
My first impression is that the writes are being processed out-of-order on
the server, so XFS is using a range of allocation sizes while growing the
file extents.
Ben
next prev parent reply other threads:[~2025-04-11 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 12:55 Async client v4 mount results in unexpected number of extents on the server Holger Hoffstätte
2025-04-11 13:29 ` Benjamin Coddington [this message]
2025-04-12 12:36 ` Holger Hoffstätte
2025-04-12 17:28 ` Benjamin Coddington
2025-04-12 19:19 ` Holger Hoffstätte
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=3696A877-3C0E-4F70-9C7E-3FD8B9AD185F@redhat.com \
--to=bcodding@redhat.com \
--cc=holger@applied-asynchrony.com \
--cc=linux-nfs@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