-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Afshin Salek wrote: | Your terminology is a bit confusing for me, so:
Sorry i should have worded this much better, | you have 1 pool (zpool create) | you have a FS called public (zfs create?) | | what do you mean by "keep on separate zfs's"? You | mean ZFS snapshot? Ok, I'll start again: I have a pool "zpool create tank [...]" Then I made a zfs "zfs create [...] tank/public" Now I want to keep the sections of public separate, i.e on individual zfs. So I do "zfs create [...] tank/public/audio" The problem is that if public is shared via smb, the user is unable to access audio. It seems that if a zfs is shared, the child zfs' are not accessible as it would if they were just subdirectories. So I can do "cd /tank/public; mkdir audio" which gives users access to public/audio via the public share, but it doesn't allow detailed management of audio as it would with individual zfs'. I hope this is a better explanation, Thanks - -- Matt Harrison [EMAIL PROTECTED] http://mattharrison.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkhjEBAACgkQxNZfa+YAUWFSfwCfQxvONHtrqsf5F2FcUNYIRA8L SDYAoL2vFdRx0WNN5wn7jnBY1ddIYod+ =zKm1 -----END PGP SIGNATURE----- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
