From: Chuck Lever via Bugspray Bot <bugbot@kernel.org>
To: anna@kernel.org, cel@kernel.org, iommu@lists.linux.dev,
jlayton@kernel.org, trondmy@kernel.org, robin.murphy@arm.com,
linux-nfs@vger.kernel.org, chuck.lever@oracle.com
Subject: Re: NFS Server Issues with RDMA in Kernel 6.13.6
Date: Tue, 01 Apr 2025 14:10:13 +0000 [thread overview]
Message-ID: <20250401-b219865c8-f01953980930@bugzilla.kernel.org> (raw)
In-Reply-To: <20250313-b219865c0-2a34cbc6e249@bugzilla.kernel.org>
Chuck Lever writes via Kernel.org Bugzilla:
Attachment 307898 shows something completely different than before:
[ 4478.512632] xfs_blockgc_flush_all+0x99/0x140 [xfs]
[ 4478.512760] xfs_trans_alloc+0x116/0x2b0 [xfs]
[ 4478.512890] xfs_trans_alloc_inode+0x7d/0x190 [xfs]
[ 4478.513012] xfs_alloc_file_space+0x1ad/0x340 [xfs]
[ 4478.513149] xfs_file_fallocate+0x243/0x4b0 [xfs]
[ 4478.513276] vfs_fallocate+0x18d/0x440
[ 4478.513294] nfsd4_vfs_fallocate+0x50/0xa0 [nfsd]
[ 4478.513351] nfsd4_allocate+0x69/0xb0 [nfsd]
[ 4478.513398] nfsd4_proc_compound+0x484/0x930 [nfsd]
[ 4478.513432] ? srso_return_thunk+0x5/0x5f
[ 4478.513447] nfsd_dispatch+0xfe/0x2e0 [nfsd]
[ 4478.513493] svc_process_common+0x352/0x7d0 [sunrpc]
[ 4478.513556] ? __pfx_nfsd_dispatch+0x10/0x10 [nfsd]
[ 4478.513600] svc_process+0x13e/0x260 [sunrpc]
[ 4478.513644] svc_recv+0x9a8/0xc40 [sunrpc]
[ 4478.513694] ? __pfx_nfsd+0x10/0x10 [nfsd]
[ 4478.513733] nfsd+0xe0/0x150 [nfsd]
[ 4478.513769] kthread+0xe7/0x120
[ 4478.513777] ? __pfx_kthread+0x10/0x10
[ 4478.513787] ret_from_fork+0x46/0x70
[ 4478.513794] ? __pfx_kthread+0x10/0x10
[ 4478.513801] ret_from_fork_asm+0x1a/0x30
Here your NFS server is waiting in the local file system for an NFSv4.2 ALLOCATE operation. Nothing to do with RDMA.
I'm at a loss to say that there is anything specific -- I think you are just at the limit that your server configuration can handle.
View: https://bugzilla.kernel.org/show_bug.cgi?id=219865#c8
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
prev parent reply other threads:[~2025-04-01 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 18:35 NFS Server Issues with RDMA in Kernel 6.13.6 Lucas via Bugspray Bot
2025-03-13 18:44 ` Chuck Lever
2025-03-13 19:20 ` Lucas via Bugspray Bot
2025-03-14 10:43 ` Robin Murphy
2025-03-14 20:26 ` Chuck Lever
2025-03-24 16:55 ` Lucas via Bugspray Bot
2025-03-24 18:35 ` Chuck Lever via Bugspray Bot
2025-03-26 23:00 ` Lucas via Bugspray Bot
2025-04-01 14:10 ` Chuck Lever via Bugspray Bot [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=20250401-b219865c8-f01953980930@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=iommu@lists.linux.dev \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=trondmy@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