I can''t get sharesmb=name= to work....it worked in b130....i''m not sure if it''s broken in 131 or if my machine is being a pain. anyways, when i try to do this: zfs set sharesmb=name=wonslung tank/nas/Wonslung i get this: cannot set property for ''tank/nas/Wonslung'': ''sharesmb'' cannot be set to invalid options i''ve googled this...and it seems to pop up a lot but so far i can''t find any solutions...it''s really driving me nuts. Also, when i try to create a NEW share the same thing happens when i use -o triggers. Please help -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100123/9c2b9708/attachment.html>
I just tried to create a new share and got the same error. -- This message posted from opensolaris.org
so this is a bug in b131? because this worked in b130 for SURE. i have shares i made in b130 with different names but in b131 i can''t do it.....it sucks because in b130 i can''t use Xorg but in b131 i can''t name shares....oh well...how do i report this as an error so they can fix it for b132? On Mon, Jan 25, 2010 at 7:10 PM, Chris Du <dilidolo at gmail.com> wrote:> I just tried to create a new share and got the same error. > -- > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100126/2012ecc9/attachment.html>
Hi Thomas, Looks like a known problem in b131 that is fixed in b132: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6912791 Unable to set sharename using zfs set sharesmb=name=<value> The workaround is to use sharemgr instead. Thanks, Cindy On 01/23/10 21:50, Thomas Burgess wrote:> I can''t get sharesmb=name= to work....it worked in b130....i''m not sure > if it''s broken in 131 or if my machine is being a pain. > > > anyways, when i try to do this: > > zfs set sharesmb=name=wonslung tank/nas/Wonslung > > i get this: > > > cannot set property for ''tank/nas/Wonslung'': ''sharesmb'' cannot be set to > invalid options > > > i''ve googled this...and it seems to pop up a lot but so far i can''t find > any solutions...it''s really driving me nuts. > > > Also, when i try to create a NEW share the same thing happens when i use > -o triggers. > > Please help > > > ------------------------------------------------------------------------ > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
i tried using sharemgr.....it didnt'' work either. or maybe i just did it wrong, could you explain what i need to do? let''s say i was trying to do this command: zfs set sharesmb=name=wonslung tank/nas/Wonslung how do i do that in sharemgr? when i tried i either got an error or it didn''t change.....i realize i may be doing it wrong. When does 132 drop? if it''s pretty soon i guess i could just wait. Thanks for the reply. On Tue, Jan 26, 2010 at 10:42 AM, Cindy Swearingen <Cindy.Swearingen at sun.com> wrote:> Hi Thomas, > > Looks like a known problem in b131 that is fixed in b132: > > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6912791 > Unable to set sharename using zfs set sharesmb=name=<value> > > The workaround is to use sharemgr instead. > > Thanks, > > Cindy > > > On 01/23/10 21:50, Thomas Burgess wrote: > >> I can''t get sharesmb=name= to work....it worked in b130....i''m not sure if >> it''s broken in 131 or if my machine is being a pain. >> >> >> anyways, when i try to do this: >> >> zfs set sharesmb=name=wonslung tank/nas/Wonslung >> >> i get this: >> >> >> cannot set property for ''tank/nas/Wonslung'': ''sharesmb'' cannot be set to >> invalid options >> >> >> i''ve googled this...and it seems to pop up a lot but so far i can''t find >> any solutions...it''s really driving me nuts. >> >> >> Also, when i try to create a NEW share the same thing happens when i use >> -o triggers. >> >> Please help >> >> >> ------------------------------------------------------------------------ >> >> >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100126/8c5a201f/attachment.html>
D''oh. I didn''t test the workaround because I was running off to a prezo. A quick test looks like you are correct. I apologize. Let me see if I can do some testing or get some more info. Thanks, Cindy On 01/26/10 09:50, Thomas Burgess wrote:> i tried using sharemgr.....it didnt'' work either. > > or maybe i just did it wrong, could you explain what i need to do? > > let''s say i was trying to do this command: > > zfs set sharesmb=name=wonslung tank/nas/Wonslung > > how do i do that in sharemgr? > > when i tried i either got an error or it didn''t change.....i realize i > may be doing it wrong. When does 132 drop? if it''s pretty soon i guess > i could just wait. > > Thanks for the reply. > > On Tue, Jan 26, 2010 at 10:42 AM, Cindy Swearingen > <Cindy.Swearingen at sun.com <mailto:Cindy.Swearingen at sun.com>> wrote: > > Hi Thomas, > > Looks like a known problem in b131 that is fixed in b132: > > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6912791 > Unable to set sharename using zfs set sharesmb=name=<value> > > The workaround is to use sharemgr instead. > > Thanks, > > Cindy > > > On 01/23/10 21:50, Thomas Burgess wrote: > > I can''t get sharesmb=name= to work....it worked in b130....i''m > not sure if it''s broken in 131 or if my machine is being a pain. > > > anyways, when i try to do this: > > zfs set sharesmb=name=wonslung tank/nas/Wonslung > > i get this: > > > cannot set property for ''tank/nas/Wonslung'': ''sharesmb'' cannot > be set to invalid options > > > i''ve googled this...and it seems to pop up a lot but so far i > can''t find any solutions...it''s really driving me nuts. > > > Also, when i try to create a NEW share the same thing happens > when i use -o triggers. > > Please help > > > ------------------------------------------------------------------------ > > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org <mailto:zfs-discuss at opensolaris.org> > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > >
On Tue, Jan 26, 2010 at 2:36 PM, Cindy Swearingen <Cindy.Swearingen at sun.com>wrote:> D''oh. I didn''t test the workaround because I was running off to a prezo. > > A quick test looks like you are correct. I apologize. > > Let me see if I can do some testing or get some more info. > > Thanks, > > Cindy > > >hehe, it''s cool. I know how THAT goes. if you figure out a work around i''d LOVE to hear it, if not i will just have to wait for 132 i guess...This isn''t the ONLY problem i''m having but it''s one of the bigger ones.....I''m also unable to get the gui for xen working but i''m going to go to the xen discuss and see if that''s a known thing as well. Thanks for checking for me =) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100126/64dbc2d9/attachment.html>
Thomas,
I think I''ve got sharemgr shares working in build 131 after all.
See the steps below.
Thanks,
Cindy
1. Create a share group, like this:
# sharemgr create -P smb myshare
2. Add the share and specify a resource name:
sharemgr add-share -r mystuff -s /tank/cindys myshare
3. Confirm the share.
# sharemgr show -vp
default nfs=()
zfs
myshare smb=()
mystuff=/tank/cindys
# cat /etc/dfs/sharetab
/tank/cindys - at myshare smb ""
On 01/26/10 13:30, Thomas Burgess wrote:>
>
> On Tue, Jan 26, 2010 at 2:36 PM, Cindy Swearingen
> <Cindy.Swearingen at sun.com <mailto:Cindy.Swearingen at
sun.com>> wrote:
>
> D''oh. I didn''t test the workaround because I was
running off to a prezo.
>
> A quick test looks like you are correct. I apologize.
>
> Let me see if I can do some testing or get some more info.
>
> Thanks,
>
> Cindy
>
>
>
> hehe, it''s cool. I know how THAT goes.
>
> if you figure out a work around i''d LOVE to hear it, if not i will
just
> have to wait for 132 i guess...This isn''t the ONLY problem
i''m having
> but it''s one of the bigger ones.....I''m also unable to
get the gui for
> xen working but i''m going to go to the xen discuss and see if
that''s a
> known thing as well.
>
> Thanks for checking for me =)
>
cool, question: what is the significance of the group? will all users still be able to attach to it? On Tue, Jan 26, 2010 at 5:27 PM, Cindy Swearingen <Cindy.Swearingen at sun.com>wrote:> Thomas, > > I think I''ve got sharemgr shares working in build 131 after all. > > See the steps below. > > Thanks, > > Cindy > > > 1. Create a share group, like this: > > # sharemgr create -P smb myshare > > 2. Add the share and specify a resource name: > > sharemgr add-share -r mystuff -s /tank/cindys myshare > > 3. Confirm the share. > > # sharemgr show -vp > default nfs=() > zfs > myshare smb=() > mystuff=/tank/cindys > > # cat /etc/dfs/sharetab > /tank/cindys - at myshare smb "" > > On 01/26/10 13:30, Thomas Burgess wrote: > > >> >> On Tue, Jan 26, 2010 at 2:36 PM, Cindy Swearingen < >> Cindy.Swearingen at sun.com <mailto:Cindy.Swearingen at sun.com>> wrote: >> >> D''oh. I didn''t test the workaround because I was running off to a >> prezo. >> >> A quick test looks like you are correct. I apologize. >> >> Let me see if I can do some testing or get some more info. >> >> Thanks, >> >> Cindy >> >> >> >> hehe, it''s cool. I know how THAT goes. >> >> if you figure out a work around i''d LOVE to hear it, if not i will just >> have to wait for 132 i guess...This isn''t the ONLY problem i''m having but >> it''s one of the bigger ones.....I''m also unable to get the gui for xen >> working but i''m going to go to the xen discuss and see if that''s a known >> thing as well. >> >> Thanks for checking for me =) >> >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100126/2b010013/attachment.html>