Longhorn rwx nfs mount issue - Protocol not supported
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-raspi (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hello,
I'm experiencing issues with longhorn rwx feature on k3s cluster since upgrade to kernel 5.15.0-1046-raspi
The symptom are exactly the same as the one describe on longhorn KB (https:/
My version deployed on my rasberry pi
root@my-pi:~$ uname -a
Linux my-pi 5.15.0-1046-raspi #49-Ubuntu SMP PREEMPT Thu Jan 18 12:45:41 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux
Mount request (with options)
root@my-pi:~$ sudo mount -t nfs -o vers=4.
mount.nfs: timeout set for Tue Feb 20 11:00:38 2024
mount.nfs: trying text-based options 'vers=4.
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
Mount request (without options)
root@my-pi:~$mount -t nfs XX.XX.XX.
mount.nfs: timeout set for Tue Feb 20 11:02:29 2024
mount.nfs: trying text-based options 'vers=4.
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4,
mount.nfs: mount(2): Protocol not supported
Created symlink /run/systemd/
mount.nfs: trying text-based options 'addr=XX.XX.XX.XX'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Timed out
mount.nfs: Protocol not supported
On another node (not using RPI) I had same issue with kernel linux-image-
Should be fixed in 5.15.137.
ommit 431a5010bce2980 9e68111c83e31bf d06d15a7d3
Author: Olga Kornievskaia <email address hidden>
Date: Mon Oct 9 10:59:01 2023 -0400
NFSv4.1: fixup use EXCHGID4_ FLAG_USE_ PNFS_DS for DS server
commit 379e4adfddd6a2f 95a4f2029b8ddcb acf92b21f9 upstream.
This patches fixes commit 51d674a5e488 "NFSv4.1: use FLAG_USE_ PNFS_DS for DS server", purpose of that
EXCHGID4_
commit was to mark EXCHANGE_ID to the DS with the appropriate
flag.
However, connection to MDS can return both EXCHGID4_ FLAG_USE_ PNFS_DS FLAG_USE_ PNFS_MDS set but previous patch would only
and EXCHGID4_
remember the USE_PNFS_DS and for the 2nd EXCHANGE_ID send that
to the MDS.
Instead, just mark the pnfs path exclusively.
Fixes: 51d674a5e488 ("NFSv4.1: use EXCHGID4_ FLAG_USE_ PNFS_DS for DS server")
Signed-off-by: Olga Kornievskaia <email address hidden>
Signed-off-by: Anna Schumaker <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>