Mounting SOFS SMB shares fails

Bug #1792580 reported by Lucian Petrut on 2018-09-14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

Ubuntu 18.04.1 LTS 4.15.0-33.36-generic
cifs-utils 2:6.8-1

Mounting scale-out SMB shares is failing.

mount -t cifs -o credentials=/tmp/creds,,uid=114,gid=119,vers=3.0,_netdev,nodfs // /tmp/test_mount
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

What works:
* mounting the share from a 16.04 host
* mounting standalone smb3 shares

Relevant error from the log (full logs attached separately):
Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc00000c9 STATUS_NETWORK_NAME_DELETED
Sep 14 11:12:05 r07-u13 kernel: /build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status code 0xc00000c9 to POSIX err -5

Share server os: Windows Server 2016 10.0.14393
PS C:\Users\jujuadmin> get-smbshare glance-images | fl *

ShareState : Online
AvailabilityType : ScaleOut
ShareType : FileSystemDirectory
FolderEnumerationMode : Unrestricted
CachingMode : Manual
SmbInstance : Default
CATimeout : 0
ConcurrentUserLimit : 0
ContinuouslyAvailable : True
CurrentUsers : 2
Description :
EncryptData : False
Name : glance-images
Path : C:\ClusterStorage\Volume1\GLANCE-IMAGES
Scoped : True
ShadowCopy : False
Special : False
Temporary : False
Volume : \\?\Volume{5faf880d-d308-4058-9ec2-d19d48089495}\
ProblemType: Bug
 total 0
 crw-rw---- 1 root audio 116, 1 Sep 7 16:51 seq
 crw-rw---- 1 root audio 116, 33 Sep 7 16:51 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Dell Inc. PowerEdge R710
Package: linux (not installed)

 PATH=(custom, no user)
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=ba74e4cf-9634-4049-abd8-0ed721836a41 ro
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
 linux-restricted-modules-4.15.0-33-generic N/A
 linux-backports-modules-4.15.0-33-generic N/A
 linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-33-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)

_MarkForUpload: False 07/23/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 6.4.0 0YDJK3
dmi.board.vendor: Dell Inc.
dmi.board.version: A14
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn0YDJK3:rvrA14:cvnDellInc.:ct23:cvr: PowerEdge R710
dmi.sys.vendor: Dell Inc.

Lucian Petrut (petrutlucian94) wrote :
Lucian Petrut (petrutlucian94) wrote :
tags: added: kernel-bug

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1792580

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
description: updated

apport information

tags: added: apport-collected bionic uec-images
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

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

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to . Please test the latest v4.19 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.


Lucian Petrut (petrutlucian94) wrote :

Hi Joseph, thanks for replying.

I've just tested the latest upstream kernel (4.19) and the issue no longer occurs. I'm attaching a log as it may help understanding the issue and pinpointing whatever patch may need to be backported.

For what is worth, I no longer get the following error after installing the latest kernel:
Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc00000c9 STATUS_NETWORK_NAME_DELETED
Sep 14 11:12:05 r07-u13 kernel: /build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status code 0xc00000c9 to POSIX err -5

Note that this did not happen after an update, it was just a vm spawned on the fly to debug this issue. Also, Ubuntu 16.04 (using 4.4.0 kernel) did not have this issue.

Lucian Petrut (petrutlucian94) wrote :
tags: added: kernel-fixed-upstream
tags: added: xenial
description: updated
description: updated
tags: removed: xenial
Joseph Salisbury (jsalisbury) wrote :

Can you see if the fix in mainline was also cc'd to 4.15 stable? That latest kernel is available from:

If 4.15.18 still exhibits the bug, we can perform a "Reverse" bisect to identify the commit that fixes the bug in 4.19

Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu Bionic):
status: New → Triaged
importance: Undecided → Medium
Changed in linux (Ubuntu):
status: Confirmed → Triaged
tags: added: kernel-da-key

I just gave 4.15.18 a try and it works properly, thanks.

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.compo/Testing/EnableProposed for documentation how to enable and use -proposed.

Thank you in advance!

Sure, I just gave the proposed kernel (4.15.0-35-generic) a try and the issue persists.

Thanks for testing -proposed! The 4.15.0-35 kernel contains the 4.15.18 upstream stable updates, which resolve this bug per comment #27. This might indicate this bug was introduced by an Ubuntu SAUCE patch, since it does not exist upstream.

We can perform a kernel bisect to identify the SAUCE patch that introduced this regression. To do that, we first need to identify the last Ubuntu kernel that did not have this bug, and the first version that does.

Can you test the following kernels:


If the 4.13.0-32 kernel also has the bug, we will have to work further back and test older kernel versions.

Thanks in advance!

Lucian Petrut (petrutlucian94) wrote :

Both 4.13.0-32 and 4.14.0-16 worked as expected.

To post a comment you must log in.