Jun 26 13:56:16 Storage shfs/user: shfs_open: lookup: Backups/new/mediacenter/test/.fuse_hidden000021340000000b (2) No such file or directory

Jun 26 13:56:17 Storage shfs/user: shfs_open: lookup: Backups/new/mediacenter/test/.fuse_hidden000021340000000b (2) No such file or directory

 

I get an immediate disconnect of an SMB share (from /mnt/user) on the client whenever my backup tool tries to create a symlink. Does not happen when SMB share is via cache drive.

The user shares (shfs /mnt/user/) does NOT support symlinks. You will need to use a different backup program or use disk shares directly (disk# /mnt/disk#)

The user shares (shfs /mnt/user/) does NOT support symlinks. You will need to use a different backup program or use disk shares directly (disk# /mnt/disk#)

 

Not strictly true.  You can indeed create symlinks.  It's netatalk that recommends not to use symlinks.

It's not a backup tool if it won't replicate the source.

 

This is a particular issue when trying to copy a Mac OS X ~/Library/Containers folder to an unRAID share. The containers folder is a sandbox for App Store applications, and needs to be preserved.

 

Is this something that can be fixed, without having to revert to a /mnt/disk# share?

 

Thanks 

Sorry, I can confirm the same issue exists while using a /mnt/disk# share.

OK - here is some more information for you. It appears this backup tool is attempting to resolve a newly created relative symlink on the share, at which point SMB will traverse outside of the share and cause all the pains.

 

If I configure the share with: "follow symlinks = no", my problem goes away as the backup tool simply can't create it due to permissions deny.

 

If I configure the share with "follow symlinks = yes AND wide links = no", the issue comes back.

 

So, either SMB is waiting for the symlink to traverse (perhaps beyond the fuse filesystem) share before checking if it exists outside of it, or there's a bug with the SMB wide link check.

 

Perhaps it's likely that there's a Samba specific problem traversing symlinks beyond the fuse filesystem?