NFS client input/output-error on kernel >=4.9

Bug #1687130 reported by Hedgehog on 2017-04-28

This bug report will be marked for expiration in 3 days if no further activity occurs. (find out why)

14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned
Zesty
Medium
Unassigned

Bug Description

I'm experiencing input/output errors on mounting NFS-shares, starting from kernel 4.9 and above.

No errors logged to syslog, but the system reports IO-errors when reading from the mount after only a few seconds. Doesn't matter which program that are accessing the disk.

My problems started after upgrading to ubuntu 17.04, but I have narrowed it down to being present from ubuntu kernel 4.9 and above by installing kernels from the ubuntu kernel ppa - i.e. when downgrading to latest 4.8-kernel from the PPA, NFS starts working as expected even on ubuntu 17.04. So it's definetely kernel related.

Probably not a hardware error either as the bug is present when NFS is mounted over both eth0 and wlan0.

Only special thing in my setup is that NFS is mounted over an ssh-tunnel.

The NFS server runs an completely up to date ubuntu 16.04 LTS install.
---
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-08-11 (991 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Package: linux (not installed)
Tags: zesty
Uname: Linux 4.8.17-040817-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to zesty on 2017-04-16 (12 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1687130

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected zesty
description: updated

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key
Changed in linux (Ubuntu Zesty):
importance: Undecided → Medium
status: New → Incomplete
Hedgehog (jimmy-serrano) wrote :

Of the kernels in the mainline ppa i can at the moment confirm that none above v4.8.17 works (ie 4.8.17-040817-generic), and all of
- v4.9.24
- v4.9.25
- v4.10-rc1
- v4.10.8
- v4.10.12
- v4.10.13
have the bug present.

I'll come back with an update after I've tested the proposed v4.11-rc8 ( http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8 )

Hedgehog (jimmy-serrano) wrote :

Bug is still present in kernel 4.11.0-041100rc8-generic from ubuntu's mainline kernel ppa. Latest kernel that is unaffected are all kernels from the ubuntu 16.10 repos, and from the mainline kernel ppa 4.8.17-040817-generic .

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Zesty):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu Zesty):
status: Confirmed → Triaged
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Bryan Quigley (bryanquigley) wrote :

Thanks for reporting this bug and helping to make Ubuntu better.

Was an upstream bug ever filed? Was a clear reproducer ever identified?

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Changed in linux (Ubuntu Zesty):
status: Triaged → Confirmed
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers