Hi Rainer, Thanks for the screenshots.
The updated package changes how the '-o vers=4' parameter works. The old / wrong behaviour would always use nfs v4.0 no matter what. All other nfs-common versions apart from the version in focal would try v4.2, then if that didn't work, then v4.1, and then v4.0, and then eventually v3.0, in a laddering fashion. You can see in your second screenshot that: $ mount -vvv -o vers=4 /srv/www/nextcloud/data ...,vers=4.2,... See, it now tries v4.2 by default? I guess your QNAP appliance is not replying to v4.2 version negotiation correctly. It is suppose to ladder down to 4.1 and then 4.0, but maybe the QNAP server doesn't reply correctly and nfs-common just waits. Can you try each specific version and report back? $ mount -vvv -o vers=4.2 /srv/www/nextcloud/data // this should hang? $ mount -vvv -o vers=4.1 /srv/www/nextcloud/data // unknown. $ mount -vvv -o vers=4.0 /srv/www/nextcloud/data // this should work As a workaround in the meantime, you can edit your /etc/fstab to set nfsvers=4.0, and you should be restored to what it was before. Just add a ".0" to the end of "nfsvers=4". Do you happen to have access to the QNAP appliance to configure NFS versions? Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056549 Title: Problems with nfs-common after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
