mount.cifs broken after update, advice?
smfrench at gmail.com
Tue Jul 12 04:36:11 UTC 2022
I was able to reproduce it to older Samba server (4.12.5) and could
workaround the Samba server bug by using mount option "compress" on
the client (which won't do anything different since it is not
supported but interestingly it avoids the problem by adding another
context at the end).
On Sun, Jul 10, 2022 at 11:08 PM Steve French <smfrench at gmail.com> wrote:
> This looks like the Samba server bug pointed out in an earlier email
> thread by Metze (fixed by
> I had trouble reproducing it on my systems but it looks like (based on
> Julian Sikorski's testing) when we fixed the netname context to not be
> null in some multichannel cases, the reordering of the contexts
> (putting netname context after the posix negotiate context) triggered
> this bug in some versions of Samba (which was fixed earlier by the
> Samba server commit above).
> On Sun, Jul 10, 2022 at 10:35 PM Brian Caine <brian.d.caine at gmail.com> wrote:
> > Hey all,
> > So I recently updated my kernel and my previously-working CIFS
> > mountpoints are broken. The server hasn't changed.
> > I can successfully access it via smbclient. Only mount.cifs is broken.
> > On the server:
> > % /usr/local/sbin/smbd --version
> > Version 4.12.15
> > On the client:
> > $ mount.cifs --version
> > mount.cifs version: 6.15
> > $ smbclient --version
> > Version 4.16.2
> > $ uname -r
> > 5.18.9-arch1-1
> > (I know it's not a vanilla kernel, so I wanted to ask for advice here
> > before making a bug report.)
> > As mentioned, smbclient still works:
> > $ smbclient -U brian //192.168.1.131/backup -c ls
> > Password for [WORKGROUP\brian]:
> > . D 0 Sat Apr 24 16:01:23 2021
> > .. D 0 Tue Dec 1 20:18:28 2020
> > brian D 0 Sat Apr 24 16:09:46 2021
> > 15119769681 blocks of size 1024. 12418540722 blocks available
> > This doesn't though:
> > # mount.cifs --verbose --verbose -o username=brian
> > //192.168.1.131/backup /tmp/foo
> > Password for brian@//192.168.1.131/backup:
> > mount error(22): Invalid argument
> > Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and
> > kernel log messages (dmesg)
> > I attached my kernel output. Is there anything there that jumps out at
> > anyone? Any easy fixes or should I look into opening a bug report?
> > Anything else I can provide, just ask.
> > Thanks,
> > Brian
More information about the samba-technical