On Fri, Mar 6, 2020 at 2:58 PM Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx> wrote: > > Steve, > > On Mon, Mar 2, 2020 at 10:12 PM Steve French <smfrench@xxxxxxxxx> wrote: > > > > Can you try an experiment with Ubuntu's newer kernel: > > > > https://wiki.ubuntu.com/Kernel/MainlineBuilds > > Or > > > > https://github.com/pimlie/ubuntu-mainline-kernel.sh > > I picked latest Debian bullseye installer. Here is what I have: > > $ uname -rvo > 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) GNU/Linux > > I am observing the same behavior with regard to 'nodfs' option. I am > required to use this option to get the first mount working. > > $ mount > [...] > //mydoma01.acme.corp/network on /tmp/z type cifs > (rw,relatime,vers=default,cache=strict,username=mmalaterre,domain=MY,uid=0,noforceuid,gid=0,noforcegid,addr=1.2.3.4,file_mode=0755,dir_mode=0755,soft,nounix,nodfs,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) > > For some reason I am getting vers=1.0 behavior (described previously): > > $ cd /tmp/z > $ cd folder2 > $ ls > subfolder2 > $ cd subfolder2/ > bash: cd: subfolder2/: Object is remote > > Ref: > > $ apt-cache policy cifs-utils > cifs-utils: > Installed: 2:6.9-1 > Candidate: 2:6.9-1 > Version table: > *** 2:6.9-1 500 > 500 http://deb.debian.org/debian bullseye/main amd64 Packages > 100 /var/lib/dpkg/status I eventually stumble upon: * https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting Which gave me a more verbose error log I found out that: [...] [ 687.037593] fs/cifs/dns_resolve.c: dns_resolve_server_name_to_ip: unable to resolve: MYSERV13 [ 687.037606] fs/cifs/cifs_dfs_ref.c: cifs_compose_mount_options: Failed to resolve server part of //MYSERV13/network to IP: -2 [...] Updating my resolve.conf from: search acme.corp to: search acme.corp mydoma01.acme.corp I was finally able to call mount -t cifs without the 'nodfs' option. The symptoms are no longer an error and simply informative: $ cd subfolder2 CIFS VFS: BAD_NETWORK_NAME: \\MYSERV13\network [...] I can finally access the content of subfolder2 without issue. -- Mathieu
