Richard L. Hamilton
2010-Oct-28 15:40 UTC
[zfs-discuss] sharesmb should be ignored if filesystem is not mounted
I have sharesmb=on set for a bunch of filesystems, including three that weren''t mounted. Nevertheless, all of those are advertised. Needless to say, the one that isn''t mounted can''t be accessed remotely, even though since advertised, it looks like it could be. # zfs list -o name,mountpoint,sharesmb,mounted|awk ''$(NF-1)!="off" && $(NF-1)!="-" && $NF!="yes"'' NAME MOUNTPOINT SHARESMB MOUNTED rpool/ROOT legacy on no rpool/ROOT/snv_129 / on no rpool/ROOT/snv_93 /tmp/.alt.luupdall.22709 on no # So I think that if a zfs filesystem is not mounted, sharesmb should be ignored. This is in snv_97 (SXCE; with a pending LU BE not yet activated, and an old one no longer active); I don''t know if it''s still a problem in current builds that unmounted filesystems are advertised, but if it is, I can see how it could confuse clients. So I thought I''d mention it. -- This message posted from opensolaris.org
Richard L. Hamilton
2010-Oct-28 15:45 UTC
[zfs-discuss] sharesmb should be ignored if filesystem is not mounted
PS obviously these are home systems; in a real environment, I''d only be sharing out filesystems with user or application data, and not local system filesystems! But since it''s just me, I somewhat trust myself not to shoot myself in the foot. -- This message posted from opensolaris.org
Alan Wright
2010-Oct-30 01:09 UTC
[zfs-discuss] sharesmb should be ignored if filesystem is not mounted
On 10/28/10 08:40 AM, Richard L. Hamilton wrote:> I have sharesmb=on set for a bunch of filesystems, > including three that weren''t mounted. Nevertheless, > all of those are advertised. Needless to say, > the one that isn''t mounted can''t be accessed remotely, > even though since advertised, it looks like it could be.When you say "advertised" do you mean that it appears in /etc/dfs/sharetab when the dataset is not mounted and/or you can see it from a client with ''net view'' on a client? I''m using a recent build and I see the smb share disappear from both when the dataset is unmounted. Alan> # zfs list -o name,mountpoint,sharesmb,mounted|awk ''$(NF-1)!="off"&& $(NF-1)!="-"&& $NF!="yes"'' > NAME MOUNTPOINT SHARESMB MOUNTED > rpool/ROOT legacy on no > rpool/ROOT/snv_129 / on no > rpool/ROOT/snv_93 /tmp/.alt.luupdall.22709 on no > # > > > So I think that if a zfs filesystem is not mounted, > sharesmb should be ignored. > > This is in snv_97 (SXCE; with a pending LU BE not yet activated, > and an old one no longer active); I don''t know if it''s still a problem in > current builds that unmounted filesystems are advertised, but if it is, > I can see how it could confuse clients. So I thought I''d mention it.
Richard L. Hamilton
2010-Nov-04 10:54 UTC
[zfs-discuss] sharesmb should be ignored if filesystem is not mounted
> On 10/28/10 08:40 AM, Richard L. Hamilton wrote: > > I have sharesmb=on set for a bunch of filesystems, > > including three that weren''t mounted. > Nevertheless, > all of those are advertised. Needless to say, > the one that isn''t mounted can''t be accessed > remotely, > even though since advertised, it looks like it could > be. > When you say "advertised" do you mean that it appears > in > /etc/dfs/sharetab when the dataset is not mounted > and/or > you can see it from a client with ''net view'' on a > client? > > I''m using a recent build and I see the smb share > disappear > from both when the dataset is unmounted.I could see it in Finder on a Mac client; presumably were I on a Windows client, it would have appeared with "net view". I''ve since turned off the sharesmb property on those filesystems, so I may need to reboot (which I''d much rather not) to re-create the problem. But if recent builds don''t have the problem, that''s the main thing. -- This message posted from opensolaris.org
Alan Wright
2010-Nov-05 04:16 UTC
[zfs-discuss] sharesmb should be ignored if filesystem is not mounted
On 11/ 4/10 03:54 AM, Richard L. Hamilton wrote:>> On 10/28/10 08:40 AM, Richard L. Hamilton wrote: >>> I have sharesmb=on set for a bunch of filesystems, >>> including three that weren''t mounted. >> Nevertheless, >> all of those are advertised. Needless to say, >> the one that isn''t mounted can''t be accessed >> remotely, >> even though since advertised, it looks like it could >> be. >> When you say "advertised" do you mean that it appears >> in >> /etc/dfs/sharetab when the dataset is not mounted >> and/or >> you can see it from a client with ''net view'' on a >> client? >> >> I''m using a recent build and I see the smb share >> disappear >> from both when the dataset is unmounted. > > I could see it in Finder on a Mac client; presumably were > I on a Windows client, it would have appeared with "net view". > I''ve since turned off the sharesmb property on those filesystems, > so I may need to reboot (which I''d much rather not) to re-create > the problem.That''s fine. If you see it again, try svcadm restart smb/server My guess is that smbd had stale cache entries for those shares. This area was reworked in snv_149 and that smbd cache was eliminated.> But if recent builds don''t have the problem, that''s the main thing.The following update was pushed to snv_149: PSARC/2010/154 Unified sharing system call 6968897 sharefs: Unified sharing system call Alan