search for: instr_files

...the destination having 'msdfsroot yes' prevents the cifs kernel >> module from following the link. I've taken a look at your traces and right off the bat I see things like this: [...] /linux-4.9.30/fs/cifs/smb1ops.c: cifs_query_symlink: target path: \smb03.physics.wisc.edu\smb\instr_files [...] /linux-4.9.30/fs/cifs/link.c: CIFS VFS: leaving cifs_get_link (xid = 35208) rc = 0 [...] /linux-4.9.30/fs/cifs/dir.c: CIFS VFS: in cifs_lookup as Xid: 35209 with uid: 1494 [...] /linux-4.9.30/fs/cifs/dir.c: parent inode = 0xffff893b14d610a8 name is: \smb03.physics.wisc.edu\smb\instr_files and...

> Which smb version are you using (mount option)? Support for DFS on smb2+ > was only added in linux 4.11. smbstatus shows the connection as NT1. DFS links do work like this: serverA_msdfsrootYES => serverB_msdfsrootNO But not like this: serverA_msdfsrootYES => serverB_msdfsrootYES Somehow the destination having 'msdfsroot yes' prevents the cifs kernel module from

...s, link points to share, link CAN be followed > trace_msdfsrootyes_share.* > > msdfs root = yes, link points to path, link CANNOT be followed > trace_msdfsrootyes_path.* In this one I still see things mixing directory separators, e.g.: Update attributes: //smb03.physics.wisc.edu/smb\instr_files inode 0xffff893c53c0e0a8 count 1 dentry: 0xffff893c596bbd80 d_time 0 jiffies 5742081270 What about making your symlink like this: ln -s 'msdfs:\\smb03.physics.wisc.edu\share\path' testback Note the use of simple quote and double _back_slash. I get unexpected result with zsh (\ g...