[zfs-discuss] ZFS Sharing over smb - permissions/access
Hello, I have setup a fileserver using zfs and am able to see the share from my mac. I am able to create/write to the share as well as read. I've ensured that I have the same user and uid on both the server (opensolaris snv101b) as well as the mac. The root folder of the share is owned by root:mygroup. When I write/create new files on the share, they get created, but the permissions are such: -- 1 aaron staff14453522 2009-01-03 15:41 myFile.txt aaron:staff is the user on the mac (leopard). When I mounted the share, I used aaron as the user. What I really would like is for this share to have newly written/created files be owned by root:mygroup. I attempted setting ACLs by various options that I used did not yield the correct result (even attempting to have everyone with full access). Is there something simple I'm missing (I hope)? Thanks! If there is any other information that I am not providing, please let me know. I do not have an smb.conf on the server that can see - all sharing is done through zfs sharesmb. Aaron -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS Sharing over smb - permissions/access
Aaron wrote: I have setup a fileserver using zfs and am able to see the share from my mac. I am able to create/write to the share as well as read. I've ensured that I have the same user and uid on both the server (opensolaris snv101b) as well as the mac. The root folder of the share is owned by root:mygroup. When I write/create new files on the share, they get created, but the permissions are such: -- 1 aaron staff14453522 2009-01-03 15:41 myFile.txt aaron:staff is the user on the mac (leopard). When I mounted the share, I used aaron as the user. What I really would like is for this share to have newly written/created files be owned by root:mygroup. This is a limitation on the part of the Mac 'smbfs' client. We use the same code base on Solaris. The code is not currently able to do I/O on the part of multiple users; the user who was authenticated at mount time owns all of the files. Also, the Mac client does not try to parse ACLs at all, so permission mode bits and reported ownership are guesses done at the client. If you set ACLs on the server, they should be enforced, even if you can't see that from the Mac. If the ownership or perm bits are in your way on the Mac, you can use smbfs mount options to get it to tell you different things, but there's no way to see the truth until more code is written. Rob T ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS Sharing over smb - permissions/access
Ok, thanks for the info - I was really puling my hair out over this. Would you know if sharing over nfs via zfs would fare any better? -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS Sharing over smb - permissions/access
Aaron wrote: Ok, thanks for the info - I was really puling my hair out over this. Would you know if sharing over nfs via zfs would fare any better? I am *quite* happy with the Mac NFS client, and use it against ZFS files all the time. It's worth the time to make sure you're using the same numeric UIDs on both the client and server if you're using the default authentication settings. Rob T ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS Sharing over smb - permissions/access
Just tired sharing over nfs and [i]much[/i] improved experience. I'll wait and see if performance becomes an issue, but this looks prety good now. The key being as you mentioned, keeping the uid/gids in sync. Thanks! Aaron -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS sharing options for Windows
Justin, Thanks for the reply In the environment I currently work in, the powers that be are almost completely anti unix. Installing the nfs client on all machines would take a real good sales pitch. None the less I am still I've pro unix I'm against putting NFS on all the PC clients as well. Putting Samba on the server and leaving the PCs alone will be much easier to manage then NFS clients. I suspect the performance and security on the PCs would be better too. Samba can authenticate to AD or have it own seperate passowrd setup. If it's a Windows shop, use AD. I've not played with the CIFS in ZFS yet, but I have older Solaris installs and Samba works well enough that I don't have a need to switch yet. playing with the client in our sandbox. As I install this on a test machine a question popped into my mind. Does this passthrough AD credentials? How does one control authentication? I haven't read anything on this yet, and will do some searching, just thought I'd pick your brain a bit. Samba does. I think CIFS in ZFS would be done with PAM? The biggest reason I am drawn to ZFS is zpool. I like the idea I can keep adding raidz arrays to a large shared pool when ever I want. With iscsi sharing I am forced to make Volumes I don't know that I really like this idea outside of the scope of making iSCSI OS partitions. For network files and shares I really want to be able utilize snapshots and other features of the ZFS filesystem. If I share out via SMB do the files not sit on the zfs FS and get captured in snapshots indiviually? My Snapshots are done in ZFS on the host. understanding was it just uses the CIFS protocol, but you still gain the benefits of the ZFS File System on the backend. The tough thing is trying to make this fit well in a Windows world. Not really. Samba makes all the OS stuff transparent to the windows user. Just like in Linux. The big change is getting an ECC, snapshotting filesystem on the host. -Craig sharesmb presents ntfs to windows, so you're still hampered by that file system's 'features' such as lots of broadcast packets and a long timeout. One other option you should consider is using NFS, for which you can install a windows client. See http://support.microsoft.com/kb/324055 or google 'nfs windows client' justin This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS sharing options for Windows
Justin, Thanks for the reply In the environment I currently work in, the powers that be are almost completely anti unix. Installing the nfs client on all machines would take a real good sales pitch. None the less I am still playing with the client in our sandbox. As I install this on a test machine a question popped into my mind. Does this passthrough AD credentials? How does one control authentication? I haven't read anything on this yet, and will do some searching, just thought I'd pick your brain a bit. The biggest reason I am drawn to ZFS is zpool. I like the idea I can keep adding raidz arrays to a large shared pool when ever I want. With iscsi sharing I am forced to make Volumes I don't know that I really like this idea outside of the scope of making iSCSI OS partitions. For network files and shares I really want to be able utilize snapshots and other features of the ZFS filesystem. If I share out via SMB do the files not sit on the zfs FS and get captured in snapshots indiviually? My understanding was it just uses the CIFS protocol, but you still gain the benefits of the ZFS File System on the backend. The tough thing is trying to make this fit well in a Windows world. -Craig sharesmb presents ntfs to windows, so you're still hampered by that file system's 'features' such as lots of broadcast packets and a long timeout. One other option you should consider is using NFS, for which you can install a windows client. See http://support.microsoft.com/kb/324055 or google 'nfs windows client' justin This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS sharing options for Windows
On May 30, 2008, at 10:45 AM, Craig Smith wrote: The tough thing is trying to make this fit well in a Windows world. If you hang all the disks off the OpenSolaris system directly, and export via CIFS ... isn't it just a NAS box from the windows perspective? If so, how is it any harder to explain/fit than a NetApp box (or any other commercial NAS solution)? -- Keith H. Bierman [EMAIL PROTECTED] | AIM kbiermank 5430 Nassau Circle East | Cherry Hills Village, CO 80113 | 303-997-2749 speaking for myself* Copyright 2008 ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] ZFS sharing options for Windows
On May 30, 2008, at 6:49 AM 5/30/, Craig J Smith wrote: It also should be noted that I am having to run on Solaris and not Opensolaris due to adaptec am79c973 scsi driver issues in Opensolaris. Well that is probably a showstopper then, since the in-kernel support isn't in the production Solaris leg yet. -- Keith H. Bierman [EMAIL PROTECTED] | AIM kbiermank 5430 Nassau Circle East | Cherry Hills Village, CO 80113 | 303-997-2749 speaking for myself* Copyright 2008 ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] ZFS sharing options for Windows
Hello, I am fairly new to Solaris and ZFS. I am testing both out in a sandbox at work. I am playing with virtual machines running on a windows front-end that connects to a zfs back-end for its data needs. As far as i know my two options are sharesmb and shareiscsci for data sharing. I have a couple questions about which way I should go. Is there a performance increase by using iSCSI? If I go with iSCSI will I have to then format NTFS on the Windows iSCSI disk? I would want the ability to create snapshots of the virtual disks, If I have to format the iSCSI target with NTFS on the windows machine ZFS would not see the individual files correct? Again this is new territory for me and I have been doing a lot of reading. Thanks in advance for any input. P.S. I know this is not an ideal situation for VM or storage, but it is what I have been given to work with. This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] ZFS sharing question.
Hello. Anyone out there remember the -d option for share? How do you set the share description using the zfs set commands, or is it even possible? Thanks! -B This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] zfs sharing
Jens Elkner wrote: The only problem I encountered with this approach was with pkgmk: If e.g. /develop/lnf/i386 is not mounted, when it runs, pkgmk doesn't trigger an automount and thinks, the target FS has a size of 0 bytes - no space available. However a short cd /develop/lnf/i386 ; cd - before pkgmk solves that problem. Another trick for this is to use a path of /develop/lnf/i386/. which will trigger an automount because of the lookup of '.'. One of my favorite automounter tricks :-) Rob T ___ zfs-discuss mailing list [EMAIL PROTECTED] http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] zfs sharing
I'm not sure if this is an nfs/autofs problem or zfs problem... But I'll try here first... On our server, I've got a zfs directory called cube/builds/izick/. In this directory I have a number of mountpoints to other zfs file systems.. The problem happens when we clone a new zfs file system, say cube/builds/izick/foo, any client system that already have cube/builds/izick mounted, can see the new directory foo, but cannot see the contents. It looks like a blank directory on the client systems, but on the server it would be fully populated with data.. All the zfs file systems are shared.. Restarting autofs and nfs/client does nothing.. The only way to fix this is to unmount the directory on the client, which can be invasive to a desktop machine.. Could there be a problem because the zfs files systems are nested? Is there a known issue with zfs-nfs interactions where zfs doesn't tell nfs properly that there has been an update, other than the just the mountpoint? thanks... Tony This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] zfs sharing
Anthony J. Scarpino wrote: I'm not sure if this is an nfs/autofs problem or zfs problem... But I'll try here first... On our server, I've got a zfs directory called cube/builds/izick/. In this directory I have a number of mountpoints to other zfs file systems.. The problem happens when we clone a new zfs file system, say cube/builds/izick/foo, any client system that already have cube/builds/izick mounted, can see the new directory foo, but cannot see the contents. It looks like a blank directory on the client systems, but on the server it would be fully populated with data.. All the zfs file systems are shared.. Restarting autofs and nfs/client does nothing.. The only way to fix this is to unmount the directory on the client, which can be invasive to a desktop machine.. Could there be a problem because the zfs files systems are nested? Is there a known issue with zfs-nfs interactions where zfs doesn't tell nfs properly that there has been an update, other than the just the mountpoint? thanks... This is a known limitation - you would need to add entries to your automounter maps to let the client know to do mounts for those 'nested' entries. We're working on it - since the client can see the new directories and detect that they're different filesystems, we could do what we call 'mirror mounts' to make them available. See http://opensolaris.org/os/project/nfs-namespace/ for more on this and other work. Rob T ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] zfs sharing
Anthony Scarpino wrote: [EMAIL PROTECTED] wrote: Anthony J. Scarpino wrote: I'm not sure if this is an nfs/autofs problem or zfs problem... But I'll try here first... On our server, I've got a zfs directory called cube/builds/izick/. In this directory I have a number of mountpoints to other zfs file systems.. The problem happens when we clone a new zfs file system, say cube/builds/izick/foo, any client system that already have cube/builds/izick mounted, can see the new directory foo, but cannot see the contents. It looks like a blank directory on the client systems, but on the server it would be fully populated with data.. All the zfs file systems are shared.. Restarting autofs and nfs/client does nothing.. The only way to fix this is to unmount the directory on the client, which can be invasive to a desktop machine.. Could there be a problem because the zfs files systems are nested? Is there a known issue with zfs-nfs interactions where zfs doesn't tell nfs properly that there has been an update, other than the just the mountpoint? thanks... This is a known limitation - you would need to add entries to your automounter maps to let the client know to do mounts for those 'nested' entries. We're working on it - since the client can see the new directories and detect that they're different filesystems, we could do what we call 'mirror mounts' to make them available. See http://opensolaris.org/os/project/nfs-namespace/ for more on this and other work. Rob T Ok... thanks for the link.. I'm happy this is known and being worked on.. Any targets yet when this would integrated? Early summer, we hope :-) Rob T ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
