Confirmed on 24.04.1 and previously on 23.10 (both server and client), also using large files (1-100GB) and 10G networking to large/fast disk arrays, which others have suggested to be a key factor. All mountpoints are running BTRFS (in some cases a brand new filesystem) without any LUKS.
My observations with throughput also match, e.g. host B as client connects to host A's nfs server and is high traffic, this fails after ~12 hours, requiring server A to reboot to recover host A as client connects to host B's nfs server but is low traffic, and mount has not failed, even if neither servers rebooted for days I have amended both my nfs.conf and fstab on all devices to force nfsvers3 only as a workaround until there's a more permanent fix, or we migrate to Debian <TASK> __schedule+0x27c/0x6b0 ? __smp_call_single_queue+0xfd/0x180 schedule+0x33/0x110 schedule_timeout+0x157/0x170 wait_for_completion+0x88/0x150 __flush_workqueue+0x140/0x3e0 ? nfsd4_run_cb+0x30/0x70 [nfsd] nfsd4_probe_callback_sync+0x1a/0x30 [nfsd] nfsd4_destroy_session+0x186/0x260 [nfsd] nfsd4_proc_compound+0x3b7/0x780 [nfsd] nfsd_dispatch+0xd7/0x220 [nfsd] svc_process_common+0x450/0x710 [sunrpc] ? __pfx_nfsd_dispatch+0x10/0x10 [nfsd] svc_process+0x132/0x1b0 [sunrpc] svc_handle_xprt+0x4d3/0x5d0 [sunrpc] svc_recv+0x18b/0x2e0 [sunrpc] ? __pfx_nfsd+0x10/0x10 [nfsd] nfsd+0x8b/0xe0 [nfsd] kthread+0xf2/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x47/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062568 Title: nfsd gets unresponsive after some hours of operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
