[Samba] What in samba 4.1 prevents a '/' share?

[David C. Rankin]

On 12/09/2013 03:15 AM, L.P.H. van Belle wrote:
> Time issues in your setup maybe? 
> 
> my samba client uses  : ( Debian Lenny ) 
> smbd -V  gives :  Version 3.5.6   ( 3.5.6~dfsg-3~bpo50+1 ) 
> cifs-utils   2:4.1-1~bpo50+1    Common Internet File System utilities
> kernel :  2.6.32-bpo.5-amd64 
> 
> 
> Best regards, 
> 
> Louis

Louis,

  Thanks for your reply. I am beginning to think it must be something weird, but
I'm not sure it is a time issue. It has to be something fundamental in smbd
4.1.X that is preventing its '/' share from being mounted on any other box. I
still have not been able to get this to work, however I can easily mount the '/'
share from any other computer. Here is my 3-computer test setup:

  On my client (hostname providence) I have:

18:01 providence:~> smbd -V
Version 3.6.7
linux 3.5.3-1
cifs-utils 5.6-2

  On the server (hostname phoinix) I have:

18:15 phoinix:~> smbd -V
Version 4.1.3
linux 3.12.6-1
cifs-utils 6.2-1

  On a second older server (hostname nemesis) I have:

18:30 nemesis:~/scr/mnt> smbd -V
Version 3.4.5-5.1-2300-SUSE-SL11.0
kernel-pae-2.6.25.20-0.7
cifs-mount-3.4.5-5.1

  Mounting the '/' config share from host *providence on nemesis* works fine:

18:31 nemesis:~/scr/mnt> sudo mount.cifs //providence/config /mnt/pv-cfg -o
username=david,uid=1000,credentials=/home/david/.dcr/mountcfile,noperm
18:31 nemesis:~/scr/mnt> l /mnt/pv-cfg
total 4
drwxr-xr-x  21 david root    0 2012-09-04 14:41 ./
drwxr-xr-x  14 root  root 4096 2013-12-28 18:29 ../
drwxr-xr-x   2 david root    0 2012-09-04 14:50 bin/
drwxr-xr-x   3 david root    0 2012-09-04 14:48 boot/
<snip>

  Mounting the '/' share from host *nemesis on providence* works fine:

18:37 providence:~/scr/mnt> sudo mount.cifs //nemesis/config /mnt/nm-cfg -o
username=david,uid=1000,credentials=/home/david/.dcr/mountcfile,noperm
18:37 providence:~/scr/mnt> l /mnt/nm-cfg
total 4
drwxr-xr-x  21 david root    0 Dec  9 11:24 .
drwxr-xr-x  11 root  root 4096 Mar  3  2011 ..
drwxr-xr-x   2 david root    0 Dec  5  2010 bin
drwxr-xr-x   4 david root    0 Mar  8  2010 boot
<snip>

  Mounting the '/' share from host *providence on phoinix* works fine:

18:54 phoinix:~/scr/mnt> sudo mount.cifs //providence/config /mnt/pv-cfg -o
username=david,uid=1000,credentials=/home/david/.dcr/mountcfile,noperm
18:55 phoinix:~/scr/mnt> l /mnt/pv-cfg/
total 4
drwxr-xr-x  21 david root    0 Sep  4  2012 .
drwxr-xr-x   9 root  root 4096 Dec 28 18:42 ..
drwxr-xr-x   2 david root    0 May 13  2011 .config
drwxr-xr-x   2 david root    0 Sep  4  2012 bin
drwxr-xr-x   3 david root    0 Sep  4  2012 boot
<snip>

  Mounting the '/' share from host *nemesis on phoinix* works fine:

18:55 phoinix:~/scr/mnt> sudo mount.cifs //nemesis/config /mnt/nm-cfg -o
username=david,uid=1000,credentials=/home/david/.dcr/mountcfile,noperm
18:57 phoinix:~/scr/mnt> l /mnt/nm-cfg
total 4
drwxr-xr-x  21 david root    0 Dec  9 11:24 .
drwxr-xr-x   9 root  root 4096 Dec 28 18:42 ..
drwxr-xr-x   2 david root    0 Dec  5  2010 bin
drwxr-xr-x   4 david root    0 Mar  8  2010 boot
<snip>

  However, attempting the mount of the '/' share from host *phoinix on anything*
else fails. The only difference I can see is this is when I'm attempting to
mount the share from 4.1.X on anything else:

18:59 nemesis:~/scr/mnt> sudo mount.cifs //phoinix/config /mnt/phx-cfg -o
username=david,uid=1000,credentials=/home/david/.dcr/mountcfile,noperm
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

18:40 providence:~/scr/mnt> sudo mount.cifs //phoinix/config /mnt/phx-cfg -o
username=david,uid=1000,credentials=/home/david/.dcr/mountcfile,noperm
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  The level 10 debugs from clients providence are contained here:

http://www.rlfpllc.com/dl/srv/smb/192.168.7.124.tar.bz2

the testparm.txt file is also in the same directory. I can't see anything in the
logs that makes sense to me, but I am no expert in looking at the nitty gritty
of the level 10 output either. Maybe Barlett has had an epiphany in the past
month or so? This isn't a huge issue, but it has me curious now. Why is this
failing? Any other thoughts would be greatly appreciated.

-- 
David C. Rankin, J.D.,P.E.