[prev in list] [next in list] [prev in thread] [next in thread]
List: zfs-discuss
Subject: [zfs-discuss] Fwd: [cifs-discuss] sharesmb on multiple fs
From: "Chris Cosby" <ccosby+zfs () gmail ! com>
Date: 2008-06-26 4:21:39
Message-ID: 1a99b5cc0806252121g75ca742bp3a48e38496230d21 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Wed, Jun 25, 2008 at 11:42 PM, Matt Harrison <
iwasinnamuknow@genestate.com> wrote:
> -----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.
>
You're absolutely correct - and it's because the "child zfs'", we'll call
them "filesystems" since that's what they are, are not directories. The OS
treats mount points differently than it does simple directories. Think of
each of those ZFS entities just as you would if they weren't mounted under
the same parent. i.e. If you had /home/floyd and /usr/local/pink - you
wouldn't try to setup a smb share under / and descend all of the way down.
The way you describe your wants, you want to create a different share for
each of the children anyway, so just do it. Oh, and this isn't a ZFS
limitation, it's an architecture limitation. i.e. You're Doing It Wrong
(TM).
>
> 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
> iwasinnamuknow@genestate.com
> 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
>
--
chris -at- microcozm -dot- net
=== Si Hoc Legere Scis Nimium Eruditionis Habes
[Attachment #5 (text/html)]
On Wed, Jun 25, 2008 at 11:42 PM, Matt Harrison <<a \
href="mailto:iwasinnamuknow@genestate.com" \
target="_blank">iwasinnamuknow@genestate.com</a>> wrote:<br><div \
class="gmail_quote"><div class="gmail_quote"><div class="Ih2E3d"> <blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> <div>-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div><div>Afshin Salek wrote:<br>
> Your terminology is a bit confusing for me, so:<br>
<br>
</div>Sorry i should have worded this much better,<br>
<div><br>
> you have 1 pool (zpool create)<br>
> you have a FS called public (zfs create?)<br>
> <br>
> what do you mean by "keep on separate zfs's"? You<br>
> mean ZFS snapshot?<br>
<br>
</div>Ok, I'll start again:<br>
<br>
I have a pool "zpool create tank [...]"<br>
<br>
Then I made a zfs "zfs create [...] tank/public"<br>
<br>
Now I want to keep the sections of public separate, i.e on individual zfs.<br>
<br>
So I do "zfs create [...] tank/public/audio"<br>
<br>
The problem is that if public is shared via smb, the user is unable to<br>
access audio. It seems that if a zfs is shared, the child zfs' are not<br>
accessible as it would if they were just subdirectories.<br>
</blockquote></div><div>You're absolutely correct - and it's because the \
"child zfs'", we'll call them "filesystems" since \
that's what they are, are not directories. The OS treats mount points differently \
than it does simple directories. Think of each of those ZFS entities just as you \
would if they weren't mounted under the same parent. i.e. If you had /home/floyd \
and /usr/local/pink - you wouldn't try to setup a smb share under / and descend \
all of the way down. The way you describe your wants, you want to create a different \
share for each of the children anyway, so just do it. Oh, and this isn't a ZFS \
limitation, it's an architecture limitation. i.e. You're Doing It Wrong (TM). \
<br>
</div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br> So I \
can do "cd /tank/public; mkdir audio" which gives users access to<br> \
public/audio via the public share, but it doesn't allow detailed<br> management \
of audio as it would with individual zfs'.<br> <br>
I hope this is a better explanation,<br>
<div><br>
Thanks<br>
<br>
- --<br>
Matt Harrison<br>
<a href="mailto:iwasinnamuknow@genestate.com" \
target="_blank">iwasinnamuknow@genestate.com</a><br> <a \
href="http://mattharrison.org" \
target="_blank">http://mattharrison.org</a><br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (MingW32)<br>
<br>
</div>iEYEARECAAYFAkhjEBAACgkQxNZfa+YAUWFSfwCfQxvONHtrqsf5F2FcUNYIRA8L<br>
SDYAoL2vFdRx0WNN5wn7jnBY1ddIYod+<br>
=zKm1<br>
-----END PGP SIGNATURE-----<br>
<div><div></div><div>_______________________________________________<br>
zfs-discuss mailing list<br>
<a href="mailto:zfs-discuss@opensolaris.org" \
target="_blank">zfs-discuss@opensolaris.org</a><br> <a \
href="http://mail.opensolaris.org/mailman/listinfo/zfs-discuss" \
target="_blank">http://mail.opensolaris.org/mailman/listinfo/zfs-discuss</a><br> \
</div></div></blockquote></div></div><font color="#888888"><br></font></div><br>-- \
<br>chris -at- microcozm -dot- net<br>=== Si Hoc Legere Scis Nimium Eruditionis Habes
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic