I've done further tests, and found that with kernels 3.13.0-128, 3.13.0-133, 3.13.0-134 and 3.13.0-135, mounting cifs folder using vers=3.0 (with no security mode manually set, ie: no option sec=ntlmsspi used) sometimes work and sometimes it doesn't, unfortunately I can't figure out what is causing this; if anyone has any ideas please let me know.
It's so weird that sometimes after a fresh boot, I can see that the mount points from the fstab aren't mounted so if I do either sudo mount -a or sudo mount -o remount -a it sometimes crashes and sometimes it works and successfully mount the folders, see below example: # Fresh boot $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty # In this example I'm using 3.13.0-128, but same behaviour with newer kernels $ uname -a Linux ruby2-staging03 3.13.0-128-generic #177-Ubuntu SMP Tue Aug 8 11:40:23 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ ll /mnt/apps total 8 drwxr-xr-x 2 root root 4096 Nov 19 2015 ./ drwxr-xr-x 9 root root 4096 Aug 10 17:54 ../ $ sudo mount -a - OR - $ sudo mount -o remount -a mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) # try again, could fail every time but sometimes it does succeeds and mount the files: $ sudo mount -a - OR - $ sudo mount -o remount -a $ ll /mnt/apps total 25 drwxrwx--- 2 root root 4096 Aug 21 14:38 ./ drwxr-xr-x 9 root root 4096 Aug 10 17:54 ../ -rw-rw---- 1 root root 0 Aug 10 21:04 test drwxrwx--- 2 root root 0 Oct 21 2015 tmp/ # Relevant entry from /etc/fstab: //some_server/Applications /mnt/apps cifs vers=3.0,iocharset=utf8,noperm,rw,uid=root,file_mode=0660,dir_mode=0770,credentials=/credentials 0 0 Cheers FedeX -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729337 Title: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: In Progress Status in linux source package in Artful: Fix Committed Bug description: == SRU Justification == The bug reporter stated they have a cluster of servers that applied Xenial updates and then were unable to mount CIFS shares after upgrading to 4.4.0-98. The same machines on 4.4.0-97 do not hit the regression. It was found that the regression is fixed by mainline commit: 4587eee04e2a ("SMB3: Validate negotiate request must always be signed"). This fix is required in all Ubuntu supported releases. Commit 4587eee04e2a landed in mailine as of 4.14-rc7. It was also cc'd to upstream stable, but it has not landed in any stable releases yet, which is the reason for this SRU. == Fix == commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd Author: Steve French <smfre...@gmail.com> Date: Wed Oct 25 15:58:31 2017 -0500 SMB3: Validate negotiate request must always be signed == Regression Potential == This patch is to fix a regression. It was also cc'd to upstream stable, so it received addition review upstream. We have a cluster of servers that applied a security update overnight and were unable to mount CIFS shares after upgrading to 4.4.0-98. The same machines on 4.4.0-97 were fine the night before, and are fine after downgrading. The only error message CIFS would report, even on verbose, was: [ 257.089876] CIFS VFS: validate protocol negotiate failed: -11 [ 257.089964] CIFS VFS: cifs_mount failed w/return code = -5 Rebooting did not help. Nor did attempting to mount the share manually using mount -t cifs. Here's the offending line from our /etc/fstab (with hostnames sanitized): //server/share /mnt/share cifs rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770 ,exec,soft,noserverino,vers=3.0 0 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Nov 1 07:56 seq crw-rw---- 1 root audio 116, 33 Nov 1 07:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 1 08:49:47 2017 HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1 InstallationDate: Installed on 2016-12-16 (319 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic root=/dev/mapper/ubuntu--template--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware 1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
