It sounds like this is/was a valid regression report. It's something
that was considered:
> e.g. 4.2 may be selected instead of 4.0 used previously. This could
have an impact on workloads if there are any regressions in switching to
4.2 from 4.0 etc.
...but on balance we chose to proceed anyway.
Hi Rainer.
I think we will leave it as is. Keep using v4.0 for now, and you should
be fine.
I'll close the bug.
Andreas, I will remove regression-update if that is okay with you.
Thanks,
Matthew
** Changed in: nfs-utils (Ubuntu Focal)
Status: New => Invalid
** Changed in: nfs-utils
Hi Matthew,
I think I will leave except you want to do some tests. I think you
tested it with a latest NFS Server version and maybe the NFS Version on
QNAP is too old and/or buggy.
Best regards
Rainer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Rainer,
Thanks for trying that out, and it is great to hear that v4.0 works for
you, and you added it to your /etc/fstab as a good workaround for the
meantime.
Are you interested in debugging why your system hangs when trying v4.2
and v4.1? or do you want to leave it there? 4.0 will keep
Dear Matthew,
I tried your commands with the following results:
$ mount -vvv -o vers=4.2 /srv/www/nextcloud/data
// this hangs?
$ mount -vvv -o vers=4.1 /srv/www/nextcloud/data
// this hang too?
$ mount -vvv -o vers=4.0 /srv/www/nextcloud/data
// this works
In the attachment you can find the
Hey Matthew,
I will try it today after the working hours.
I have access to the QNAP but I can only activate 3.x and/or 4.x on the
Webinterface (See here for an example:
https://www.qnap.com/en/how-to/faq/article/how-to-access-files-on-nas-via-nfs-from-unixlinux-clients).
I checked the
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
Hi,
in the attachment you can find a screenshot about the /etc/fstab.
Additionally you can find a screenshot about the mount result. The
command hung. The timeout time was already reached but the command is
running. This is the only output.
The NFS Server should be version 4.x. QNap can run both
And here the mount command screenshot
** Attachment added: "mount"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+attachment/5754915/+files/2.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Rainer,
I developed the nfs-utils update of 1:1.3.4-2.5ubuntu3.6, and I am very
interested to hear more about the possible regression.
The intention was to fix version negotiation when using the '-t nfs4' or
'-o vers=4' parameters in your mount command. You can find more about it
here:
> That means if I enter "mount /my_nfs_path/" the command is running
endless and nothing happens.
What's your /etc/fstab line for this mount point?
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: ubuntu => nfs-utils (Ubuntu)
** Tags removed: nfs
** Tags added: focal
--
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
** Project changed: launchpad => ubuntu
--
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:
13 matches
Mail list logo
