Linux kernel >= 5.16.10 and issues with Qnap NFSv4

[saldsl]

I just want to raise attention and warn everyone here that changes in NFSv4 introduced in Linux kernel 5.16.10 are not compatible with Qnap NASes.
You can get the details at:
https://bugzilla.redhat.com/show_bug.cgi?id=2055362
where some folks have pinpointed where the problem lays.

I hope this will avoid someone else to screw up wondering why their shares are not mounted anymore...

[prox612]

I started using NFSv3 till NFS4 gets fixed. There is also a debian bug report on this.

[prox612]

https://bugs.debian.org/cgi-bin/bugrepo ... ug=1006518


This is the bug report not sure if its related or not. However the same symptoms are happening.

[_tus_]

Temporary workaround on my side, force vers=4.0 in the /etc/fstab of the client.

[prox612]

Temporary workaround on my side, force vers=4.0 in the /etc/fstab of the client.

This seems to work nfsvers=4.0 setting instead of nfsvers=4.

[greyman1956]

I can confirm that this is happening on my QTS 5.0.0.1932 which has kernel-5.10.60 with client Fedora F35 (kernel-5.16.10+).

I am mounting through fstab :
nfs4 x-systemd.automount,x-systemd.idle-timeout=15min,rw,sync 0 0

[waldauf]

I confirm that mount parameter

Code: Select all

-o nfsvers=4.0

fixed my problem with the hanged-out command mount.nfs.

Arch Linux
Kernel: 5.17.1-arch1-1

Thx!

[zeddock]

I confirm that mount parameter

Code: Select all

-o nfsvers=4.0

fixed my problem with the hanged-out command mount.nfs.

Arch Linux
Kernel: 5.17.1-arch1-1

Thx!

Can you please give a little more detail here?
I am a noob and mostly forgetful, so I set things up like a mount for my QNAP NAS, and I forget it, and just use it.
It is broken now and I am trying to find a way to use this for work until a fix comes out.
My way of mounting before was through /etc/fstab with the line:

Code: Select all

10.0.0.173:/NAS_BRIDGE /home/jim/NAS_LINK nfs4 defaults,_netdev 0   0

...which does not work now.
if I offer sudo mount -a in a terminal it just hangs there. Oh! lights just went off! That is what you meant by "hanged-out command"?

Anyway... if you have found a way to make this work in my Manjaro system, please give the details so I might have a chance to mirror your success?

Thank you kindly!

[zeddock]

Wowser!
I figured it out. It took most of the day! And I will forget in a few weeks, but for right now I did it:
I was able to apply the above that @waldauf confirmed: -o nfsvers=4.0.
To do this:
1. Verify the mount is not there. from the terminal I gave "sudo umount /home/jim/NAS_LINK" where NAS_LINK is the directory I used to use to mount to.
2. I offered to mount all but with the new option: "sudo mount -a -o nfsvers=4.0 "
3. It didn't hang the terminal and I could browse to the NAS_LINK directory and see my NAS files and folders!

So, now I had to figure out how to get that option into the fstab.
In reading I found that nsf4 is deprecated but still usable. It should change to only "nfs".
Then, I found that unlike other file systems, nfs has a "helper" it refers to. So you have to put the options into the options area.
I found this meant behind "defaults," and so this works in the fstab for me:
"10.0.0.173:/NAS_BRIDGE /home/jim/NAS_LINK nfs defaults,nfsvers=4.0,_netdev 0 0"

After saving that, I:
1. Go back to terminal and unmount. "sudo umount /home/jim/NAS_LINK"
2. Now, I just tell it to mount all that are in fstab: "sudo mount -a"

Go checked the directory, and my NAS stuff is there.

Hope it works for you!

[mrobin604]

I had this issue last night when I upgraded my client machines to 22.04 LTE (Jammy Jellyfish). I went through a couple hours of debugging last night, and eventually added nfsvers=4.0 to my /etc/fstab entry, and it worked for me. Note that nfsvers=4 will NOT work, as it will still try vers 4.2 and hang.

[jonnypuma]

I had this issue last night when I upgraded my client machines to 22.04 LTE (Jammy Jellyfish). I went through a couple hours of debugging last night, and eventually added nfsvers=4.0 to my /etc/fstab entry, and it worked for me. Note that nfsvers=4 will NOT work, as it will still try vers 4.2 and hang.

Could you please explain how you edit the fstab entry? I don't know linux but know how to use putty and run commands. NFS just stopped working after latest upgrade for me.

[OneCD]

Could you please explain how you edit the fstab entry?

The fstab file mentioned is located on the client machine. You don’t need to edit inside the NAS.

[jonnypuma]

Could you please explain how you edit the fstab entry?

The fstab file mentioned is located on the client machine. You don’t need to edit inside the NAS.

Thanks for the reply. I found out why my NFS wasn't working. After updating QTS it seems Advanced Folder Permissions and Windows ACL had been enabled for some reason. All good after disabling them.