I've noticed that Vasily's commit has meanwhile landed in linux-next,
so I took it from there and applied it to noble master-next,
but it failed due to changed context.
Hence I did a bit of backporting work and got now it in.
I triggered appropriate kernel test builds here:
This is a valid bug but since IBM has a fix at upstream that will
trickle down to our stable kernels, I am un-assigning myself.
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Assignee: Anthony Wong (anthonywong) => (unassigned)
--
You received
Adding a release notes task to put a note under "known issues".
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060217
Marking the userspace component (src:nfs-utils) task as invalid, since
it's a bug in the kernel.
** Changed in: nfs-utils (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Vasily. After it is merged by upstream maintainer, maybe you can
send it to ubuntu kernel list as well, or wait until noble update to
future upstream stable release since the patch has been cced to
sta...@vger.kernel.org and also has fixes tag.
--
You received this bug notification
Thanks for the info, and I tested v6.6 which was fine. Will dig into
about the change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060217
Title:
NFSv4 fails to mount in noble/s390x
To manage
That would be
https://github.com/torvalds/linux/commit/fce7913b13d0270bcf926f986b7ef329e2e56eec
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060217
Title:
NFSv4 fails to mount in noble/s390x
To
> Could I know the kernel version which use for below test?
Search for "testbed running kernel". In the case of that test, it's:
859s autopkgtest [01:53:38]: testbed running kernel: Linux 6.6.0-14-generic
#14-Ubuntu SMP Thu Nov 30 09:46:34 UTC 2023
--
You received this bug notification because
So mount v4 returns 32 (probably means EPIPE) but v3 returns 0.
ubuntu@nfs:~$ sudo strace -e mount mount localhost:/home /mnt/nfs_home -o vers=4
mount.nfs: mount system call failed for /mnt/nfs_home
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=1830, si_uid=0,
si_status=32,
I have GuoqingJiang access to the s390x vm where this bug can be
observed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060217
Title:
NFSv4 fails to mount in noble/s390x
To manage notifications
Perhaps try an older kernel, from when the test last passed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060217
Title:
NFSv4 fails to mount in noble/s390x
To manage notifications about this bug
** Tags added: architecture-s39064 bugnameltc-206018 severity-high
targetmilestone-inin---
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060217
Title:
NFSv4 fails to mount in noble/s390x
To
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Tags added: s390x
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => bugproxy (bugproxy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Andreas, I'd like to take a look, could you please let me know how to
access your vm? Because I don't have s390 hw.
BTW, seems it is fine for both amd64 and arm64.
https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/amd64
https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/arm64
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Anthony Wong (anthonywong)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060217
Title:
NFSv4 fails to mount in noble/s390x
To manage
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060217
Title:
NFSv4 fails to mount in noble/s390x
To manage notifications about this bug go to:
I have a VM where this can be reproduced, if anyone is interested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060217
Title:
NFSv4 fails to mount in noble/s390x
To manage notifications about
> Does running `mount -vvv ...` provide more information?
Nope, same as single -v:
root@nfs:~# mount /mnt/nfs_home -vvv
mount.nfs: timeout set for Mon Apr 8 15:48:10 2024
mount.nfs: trying text-based options
'vers=4.2,addr=127.0.0.1,clientaddr=127.0.0.1'
mount.nfs: mount(2): Input/output
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- Just filing the bug now to keep track of it. No troubleshooting done
- yet.
-
https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x
Looks like it has been failing for a long
I don't think it's Kerberos related. The manual reproducer is a plain mount
localhost, without Kerberos.
The same simple localhost setup was working in mantic. I then dist upgraded
the VM to noble, and it started failing.
On Sun, 7 Apr 2024, 18:10 Bryce Harrington, <2060...@bugs.launchpad.net>
Does running `mount -vvv ...` provide more information?
I notice of the 3 test cases in the dep8 that it's the 2 NFSv4 w/
kerberos ones failing, and the simple nfsv3 one passes. Could it be
something to do with kerberos or its configuration? Like, could it be
authorizing a network IP other than
I enabled rpc debugging with rpcdebug (after fixing an off-by-one strcpy
error), but the logs don't mean much to me.
** Attachment added: "rpcdebug.log"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060217/+attachment/5761997/+files/rpcdebug.log
--
You received this bug
Verbose mount:
# mount localhost:/home /mnt/nfs_home -v
mount.nfs: timeout set for Sun Apr 7 19:09:07 2024
mount.nfs: trying text-based options
'vers=4.2,addr=127.0.0.1,clientaddr=127.0.0.1'
mount.nfs: mount(2): Input/output error
mount.nfs: mount system call failed for /mnt/nfs_home
--
You
23 matches
Mail list logo
