Re: [cifs-discuss] CIFS and .zfs/previous versions
Ok, sorry that I pull up this old topic. But yesterday I have observed on our osol cifs server, that also for normal shares this problem occurs. What it is here: * Setup a box in ad mode (ldap + kerberos, ad based uids/gids) * Join with smbadm * ... * autosnapping and all that * then add another bunch of disk space to have a dedicated data pool * zpool... crate... * mount it on /export/data * create a dataset Sekretariat = data/Sekretariat 8,12G 232G 6,77G /export/data/Sekretariat Now create 2 subdirs /export/data/Sekretariat/Sekretariat-A and /export/data/Sekretariat/Sekretariat-B * set acls correctly (Domain\ Admins and Sekretariat group should have access) * use sharemgr to create a share group sekretariat publishing to the servers ad space * add both directories as individual shares * ensure snappshots are created and all is fine Now have a look to previous versions tab from a win7 client, here it always stays empty on everything in the share. Some month ago there was only one share pointing to /export/data/Sekretariat (the root of the dataset), previous versions were working fine. Due to my boss wants to have this separated I altered the share structure, with the result that now the users can't retrieve previous versions of their files as this tab now stays completely empty. Florian Am 11.06.2010 22:54, schrieb Alan Wright: Previous Versions should work from any share, anywhere in the directory hierarchy. I suspect this may be an smbautohome share problem. We'll look into it. Alan On 06/11/10 07:49 AM, MichaelHoy wrote: We have a zpool with a volume and in that volume we have a number of directories which are dynamically shared via smbautohome. e.g. zpool pstuds, volume a and directory a1234567. The server is a member of an AD. The directory name matches the local user account (local for setting ACLs) which maps (idmap) to the AD user. Works like a charm. By the way, we needed to use a directory for the home space as opposed to a volume since we have 50k users’ home directories. Trouble is…I can’t see the snapshot directory or view previous-versions whilst in the users’ home folder. If I share the volume which the directory sits in then I can however explore the UNC path (\\server\pstuds_a\.zfs\snapshot\mhtest\a1234567) and see those files which I have deleted. The question is, should I be able to explore/previous-versions of the snapshots when I’m in a directory of a volume or are snapshots only visible from the root of the volume? Thanks for taking the time to read this. Michael ___ cifs-discuss mailing list cifs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/cifs-discuss smime.p7s Description: S/MIME Cryptographic Signature ___ cifs-discuss mailing list cifs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
Re: [cifs-discuss] CIFS and .zfs/previous versions
zfs is only ever visible at the root of a dataset. We can't reproduce the nested directory Previous Versions problem. Can you provide a network capture (wireshark) for the nested directory scenario? If you provide a capture, please also include the smbautohome file, 'ls -lVd' output of the target directory and details of the user accessing the share. Output from cifs-gendiag would also be good. Thanks, Alan MichaelHoy wrote: Thanks for the prompt responses. If the destination of the smbautohome is a volume then yes, I concur. Previous Versions works and .zfs is visible e.g. zpool pstuds, volume a, volume a1234567. My problem occurs when the destination is a directory nested within a volume e.g. zpool pstuds, volume a, directory a1234567. I cannot see .zfs or Previous Versions when I use this hierarchy unless as I’ve already explained, I point to a higher level UNC at the volume level which is not ideal. Other than set an ACL on the directory, I’ve altered nothing from the default so I think this should work. ___ cifs-discuss mailing list cifs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
Re: [cifs-discuss] CIFS and .zfs/previous versions
On 06/16/10 01:26 AM, Florian Manschwetus wrote: Am 16.06.2010 10:04, schrieb Alan Wright: Florian Manschwetus wrote: Am 11.06.2010 16:49, schrieb MichaelHoy: We have a zpool with a volume and in that volume we have a number of directories which are dynamically shared via smbautohome. e.g. zpool pstuds, volume a and directory a1234567. The server is a member of an AD. The directory name matches the local user account (local for setting ACLs) which maps (idmap) to the AD user. Works like a charm. By the way, we needed to use a directory for the home space as opposed to a volume since we have 50k users’ home directories. Trouble is…I can’t see the snapshot directory or view previous-versions whilst in the users’ home folder. If I share the volume which the directory sits in then I can however explore the UNC path (\\server\pstuds_a\.zfs\snapshot\mhtest\a1234567) and see those files which I have deleted. The question is, should I be able to explore/previous-versions of the snapshots when I’m in a directory of a volume or are snapshots only visible from the root of the volume? Thanks for taking the time to read this. Michael Same effect here, we have smbautohomes on \\server\username and as unbrowseable share \\server\homes\username \\server\homes is equal to dataset (\export\data(the pool)\users) when browsing \\server\username the previous versions in properties finds nothing \\server\homes\username previous versions in properties works perfectly, even for subdirectories and files would be nice to know a workaround To investigate, please provide: - a network capture (wireshark) and 'ls -lVd' for the working scenario - a network capture and 'ls -lVd' for the failing scenario uhm it is the same scenario, the same files, the same data, just two different shares? Apparently it's not the same scenario to the software because on your system one scenario works and one doesn't work. If you're not comfortable providing diagnostic data that's fine but we can't investigate the problem without it. - user details for users accessing the shares normal ad users or admins it is all the same, just add (in our structure) \homes between \\server\username and you get the previous versions, use the autohome (\\server\username) and you have no previous versions. \\server\homes points to the dataset mounted at /export/data/users/ - your smbautohome file # cat /etc/smbautohome * /export/data/users/ This information is incomplete. For example, should I assume that you relocate the home directories and update all appropriate configuration files, including /etc/smbautohome, for each scenario? If you provide all the requested information for each scenario, we can see what's going on instead of having to make educated guesses based on partial descriptions. Alan - output from cifs-gendiag Thanks, Alan ___ cifs-discuss mailing list cifs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/cifs-discuss ___ cifs-discuss mailing list cifs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
Re: [cifs-discuss] CIFS and .zfs/previous versions
For other data I will have a look tomorrow, but - user details for users accessing the shares normal ad users or admins it is all the same, just add (in our structure) \homes between \\server\username and you get the previous versions, use the autohome (\\server\username) and you have no previous versions. \\server\homes points to the dataset mounted at /export/data/users/ - your smbautohome file # cat /etc/smbautohome * /export/data/users/ This information is incomplete. For example, should I assume that you relocate the home directories and update all appropriate configuration files, including /etc/smbautohome, for each scenario? Sorry maybe I missunderstood you, but what should I relocate where, wtf? I touched eigther the autohome nor the dataset or share configuration since 6 month. And for sure I've not moved around the 1/2 T of data. Autohomes provides a share to personal data for each user personal. the homes share exports unconditionally all dirs in /export/data/users, for administrational or foreign access purposes. If a user opens his personal files with \\server\username there are no previous versions found. If the same user on the same client now just inserts a \homes (leads to \\server\homes\username) he immediatly gets all previous versions fine. if he removes \homes from path and looks in preference for previous versions they are gone. But he still has the exactly same actual data. If he deletes a file it looks lost here, adding \homes it is also gone, but previous versions are now there and allowing to easily restore that file and yes then it is also back when using the autohome-share. So what scenario, so what should i move when? I would guess that osol looks in shareroot for .zfs, then it would find it using \\server\homes but not when using \\server\username as those are no separate datasets. Florian If you provide all the requested information for each scenario, we can see what's going on instead of having to make educated guesses based on partial descriptions. Alan smime.p7s Description: S/MIME Cryptographic Signature ___ cifs-discuss mailing list cifs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
Re: [cifs-discuss] CIFS and .zfs/previous versions
Thanks for the prompt responses. If the destination of the smbautohome is a volume then yes, I concur. Previous Versions works and .zfs is visible e.g. zpool pstuds, volume a, volume a1234567. My problem occurs when the destination is a directory nested within a volume e.g. zpool pstuds, volume a, directory a1234567. I cannot see .zfs or Previous Versions when I use this hierarchy unless as I’ve already explained, I point to a higher level UNC at the volume level which is not ideal. Other than set an ACL on the directory, I’ve altered nothing from the default so I think this should work. -- This message posted from opensolaris.org ___ cifs-discuss mailing list cifs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
Re: [cifs-discuss] CIFS and .zfs/previous versions
Am 11.06.2010 16:49, schrieb MichaelHoy: We have a zpool with a volume and in that volume we have a number of directories which are dynamically shared via smbautohome. e.g. zpool pstuds, volume a and directory a1234567. The server is a member of an AD. The directory name matches the local user account (local for setting ACLs) which maps (idmap) to the AD user. Works like a charm. By the way, we needed to use a directory for the home space as opposed to a volume since we have 50k users’ home directories. Trouble is…I can’t see the snapshot directory or view previous-versions whilst in the users’ home folder. If I share the volume which the directory sits in then I can however explore the UNC path (\\server\pstuds_a\.zfs\snapshot\mhtest\a1234567) and see those files which I have deleted. The question is, should I be able to explore/previous-versions of the snapshots when I’m in a directory of a volume or are snapshots only visible from the root of the volume? Thanks for taking the time to read this. Michael Same effect here, we have smbautohomes on \\server\username and as unbrowseable share \\server\homes\username \\server\homes is equal to dataset (\export\data(the pool)\users) when browsing \\server\username the previous versions in properties finds nothing \\server\homes\username previous versions in properties works perfectly, even for subdirectories and files would be nice to know a workaround Florian smime.p7s Description: S/MIME Cryptographic Signature ___ cifs-discuss mailing list cifs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
Re: [cifs-discuss] CIFS and .zfs/previous versions
Initial tests would seem to indicate that Previous Versions is working on smbautohome shares. Alan On 06/11/10 07:49 AM, MichaelHoy wrote: We have a zpool with a volume and in that volume we have a number of directories which are dynamically shared via smbautohome. e.g. zpool pstuds, volume a and directory a1234567. The server is a member of an AD. The directory name matches the local user account (local for setting ACLs) which maps (idmap) to the AD user. Works like a charm. By the way, we needed to use a directory for the home space as opposed to a volume since we have 50k users’ home directories. Trouble is…I can’t see the snapshot directory or view previous-versions whilst in the users’ home folder. If I share the volume which the directory sits in then I can however explore the UNC path (\\server\pstuds_a\.zfs\snapshot\mhtest\a1234567) and see those files which I have deleted. The question is, should I be able to explore/previous-versions of the snapshots when I’m in a directory of a volume or are snapshots only visible from the root of the volume? Thanks for taking the time to read this. Michael ___ cifs-discuss mailing list cifs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
