James A. Dinkel
2006-Nov-28 18:19 UTC
[Samba] Shadow Copy Client blank, with error in logs
One computer will show the previous versions of files just fine, but every other computer I've installed the Microsoft Shadow Copy Client on will not show any previous versions. The Previous Versions tab is just blank. In the samba log, I get this: [2006/11/28 12:02:02, 0] modules/vfs_shadow_copy.c:shadow_copy_opendir(81) shadow_copy_opendir: SMB_VFS_NEXT_OPENDIR() failed for [Folder/file.txt] This is logging in as the same user on each machine. James Dinkel Network Engineer Butler County of Kansas There are 10 types of people in the world: those who understand binary, and those who don't.
Michael Waterman
2006-Nov-28 20:47 UTC
[Samba] Shadow Copy Client blank, with error in logs
There's a module for vss on Linux???? -----Original Message----- From: samba-bounces+m.waterman=xs4all.nl@lists.samba.org [mailto:samba-bounces+m.waterman=xs4all.nl@lists.samba.org] On Behalf Of James A. Dinkel Sent: Tuesday, November 28, 2006 7:19 PM To: samba@lists.samba.org Subject: [Samba] Shadow Copy Client blank, with error in logs One computer will show the previous versions of files just fine, but every other computer I've installed the Microsoft Shadow Copy Client on will not show any previous versions. The Previous Versions tab is just blank. In the samba log, I get this: [2006/11/28 12:02:02, 0] modules/vfs_shadow_copy.c:shadow_copy_opendir(81) shadow_copy_opendir: SMB_VFS_NEXT_OPENDIR() failed for [Folder/file.txt] This is logging in as the same user on each machine. James Dinkel Network Engineer Butler County of Kansas There are 10 types of people in the world: those who understand binary, and those who don't. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
On Tue, Nov 28, 2006 at 12:19:15PM -0600, James A. Dinkel wrote:> One computer will show the previous versions of files just fine, but > every other computer I've installed the Microsoft Shadow Copy Client on > will not show any previous versions. The Previous Versions tab is just > blank. In the samba log, I get this: > > > > [2006/11/28 12:02:02, 0] > modules/vfs_shadow_copy.c:shadow_copy_opendir(81) > > shadow_copy_opendir: SMB_VFS_NEXT_OPENDIR() failed for > [Folder/file.txt] > > > > > > This is logging in as the same user on each machine.Can you send in a debug level 10 please ? Jeremy.
James A. Dinkel
2006-Nov-28 21:58 UTC
[Samba] Shadow Copy Client blank, with error in logs
Is this a bug?! Ok, upon further investigation, I've discovered that the Previous Versions does not work when access the share through a "nested" drive mapping. By "nested" I mean we have the H: drive in Windows mapped to \\SambaServer\share\DepartmentFolder. If I create a drive mapping, say X: drive to \\SambaServer\share, then the Previous Version show up when going through the X: drive (or the UNC path) but NOT when going through the H: drive. However, I have found a fix for this (I'll get to it in a little bit), but it's sloppy. This is a big problem for us, because all our users have the H: drive mapped to a folder below the share based on what department they are in. So the fix is: I created a symlink under the nested folder ("DepartmentFolder" in this case) that pointed to the same folder in the snapshot. I gave the symlink the "@GMT-" name that the shadow_copy module requires, and of course created script that destroys and creates this link along with the snapshots. I don't know if this is an issue with the Previous Versions client, but I would think the shadow_copy module could be patched so that it knows to look back at the root of the file share for the snapshot. James Dinkel
James A. Dinkel
2006-Nov-29 00:52 UTC
[Samba] Shadow Copy Client blank, with error in logs
Well, it looks like this only fixed it for admin users. The Previous Versions is still showing up blank for regular valid users. I'll look more into it, and try to get a debug 10 log tomorrow. James Dinkel
James A. Dinkel
2006-Nov-29 15:04 UTC
[Samba] Shadow Copy Client blank, with error in logs
Ok, I figured this out, too. I expected that THIS was a permissions issue. I add o+x permission to the folder containing the snapshots and all is well. I still wish though, that there was a better way to taking care of the nested drive mappings than having to create a symlink for every drive mapping... :( James Dinkel -----Original Message----- From: James A. Dinkel Well, it looks like this only fixed it for admin users. The Previous Versions is still showing up blank for regular valid users. I'll look more into it, and try to get a debug 10 log tomorrow. James Dinkel