[Samba] dfs problems addressed in 3.0.25b?

[Jeremy Allison]

On Wed, Jul 04, 2007 at 07:11:27AM +0000, julian at precisium.com wrote:
> >  
> Reproducing it is likely to be tricky - because it's intermittent. It 
> happens maybe every few days for me.
> 
> This configuration exhibits the behaviour:
> 
> smb.conf
> ------------------------------------
> [global]
>    workgroup = SOMEDOMAIN
>    netbios name = dfsserver
>    host msdfs = yes
>    server string = "FreeBSD - Samba %v - DFS"
>    guest account = nobody
>    guest ok = yes
>    inherit permissions = yes
>    create mask = 0777
>    directory mask = 0777
>    unix extensions = no
>    follow symlinks = yes
>    wide symlinks = yes
> 
> 
> [net]
>    read only = no
>    path = /dfs/net
>    msdfs root = yes
>    inherit permissions = yes
>    browseable = yes
> 
> [ops]
>    read only = no
>    path = /dfs/ops
>    msdfs root = yes
>    inherit permissions = yes
>    browseable = yes
> 
> ------------------------------------
> 
> in the folder: /dfs/net/machinename
> > ln -s msdfs:machinename.somedomain.com\sharename  sharename
> 
> ------------------------------------
> now:
> \\dfsserver\net\machinename\sharename\problemfolder
> may after some unknown period.. display the same listing as:
> \\dfsserver\net\machinename\sharename\
> 
> \\dfsserver.somedomain.com\net\machinename\sharename\problemfolder might 
> however show the correct listing.
> 
> The duplication is not infinitely recursive..
> ie \\dfsserver\net\machinename\sharename\problemfolder\problemfolder    
> shows the normal listing that should be at 
> \\dfsserver\net\machinename\sharename\problemfolder
> 
> ------------------------------------
> I just did more opening and closing of explorers and browsing back and 
> forth...
> and for the first time I've seen two folders (under the same parent) 
> simultaneously showing the wrong listing.
> 
> 
> To further complicate..
> It may be related to the fact that  under a separate share on the 
> dfsserver there is also a link (this time to a point beyond the 
> destination share):
> 
> /dfs/ops
> >ln -s 
> msdfs:machinename.somedomain.com\sharename\siblingofproblemfolder   
> siblingofproblemfolder
> 
> ie an alternative way to get to a sibling of the problem subfolder(s)  
> so the following are equivalent:
> \\dfsserver.somedomain.com\ops\siblingofproblemfolder 
> \\dfsserver.somedomain.com\net\machinename\sharename\siblingofproblemfolder

Doesn't sound like a Samba bug to be honest. Have you looked
into MS DFS bugs ?

What filesystem are you running this on ?

Jeremy.