Dear Maintainer,
we have the same problem on our 7.1 server (3.2.0-4-amd64 #1 SMP Debian 3.2.51-1
x86_64 GNU/Linux) with samba (2:3.6.6-6+deb7u2).
If the snapdir path is wrong there is an errormessage in the logs but if the
path is correct there is no logging, but it won't show files in the windows
recovery tab.
To be sure that the error is not in my configuration, I tried it on my ubuntu
workstation samba 3.6.9 and it worked, after setting a relative snapdir.
--- smb.conf ---
...
unix extensions = no
wide links = yes
[projekte]
...
vfs objects = shadow_copy2
shadow:snapdir = ../snapshots
shadow:basedir = /data/projekte
shadow:sort = desc
---
After that I compiled vfs_shadow_copy2.c from 3.6.22 and give it a try with my
3.6.6 with the above config and get this errormessage:
log.smbd.172.17.64.17:[2014/01/08 23:19:52.168108, 2]
modules/vfs_shadow_copy2.c:894(shadow_copy2_get_shadow_copy2_data)
log.smbd.172.17.64.17: shadow_copy2: SMB_VFS_NEXT_OPENDIR() failed for
'/data/../snapshots/' - No such file or directory
after correcting the snapdir to: "shadow:snapdir = snapshots" there is no
logging and no files are shown in the windows recovery tab.
# ls -l /data/snapshots/
lrwxrwxrwx 1 root root 45 Jan 9 10:00 @GMT-2014.01.09-08.00.11 ->
/data/snapshots/hourly.2/local/data/projekte/
lrwxrwxrwx 1 root root 45 Jan 9 10:00 @GMT-2014.01.09-09.00.14 ->
/data/snapshots/hourly.1/local/data/projekte/
lrwxrwxrwx 1 root root 45 Jan 9 10:00 @GMT-2014.01.09-10.00.13 ->
/data/snapshots/hourly.0/local/data/projekte/
drwxr-xr-x 3 root root 4096 Jan 9 10:00 hourly.0
drwxr-xr-x 3 root root 4096 Jan 9 09:00 hourly.1
drwxr-xr-x 3 root root 4096 Jan 9 08:00 hourly.2
"ls" on the @GMT* shows the same files like a "ls" on /data/projekte, I also
tried shorter symlinks "/data/snapshots/hourly.2/local"
