[cifs-discuss] [zfs-discuss] sharesmb settings not working with some filesystems

[Afshin Salek]

What's the output of "ls -vd" on these two broken directories?
(This will show you the ACL of the directory)

What kind of client are you using and who's the user you are
connecting with to these shares?

Is your CIFS server in domain mode or workgroup mode?
# smbadm list

How does your idmap setup and cache look like?
# idmap list
# idmap dump

Afshin

Benjamin Staffin wrote:
> (-zfs-discuss, +cifs-discuss)
> 
> On Tue, May 6, 2008 at 12:00 PM, Benjamin Staffin <benley at zoiks.net> wrote:
>> On Mon, May 5, 2008 at 10:23 PM,  <Rob at logan.com> wrote:
>>>> cannot share 'tank/software': smb add share failed
>>> you meant to post this in storage-discuss
>>> but type:
>>>
>>> chmod 777 /tank/software
>>> zfs set sharesmb=name=software tank/software
>> Wow.  Sometimes the simplest solutions are the hardest to see.  The
>> directory had gotten set to mode 000,and I have absolutely no idea
>> how.  A simple chmod 755 made everything happy.
>>
>> *sigh*  Thank you.
> 
> So, now I have another problem.
> 
> I am quite sure that the permissions are set correctly on this volume
> now.  I also ended up fixing a bunch of other parts of the system -
> including /, which had become owned by a uid other than 0 somehow.
> Very strange, and probably a result of me fat-fingering something
> along the way.  Or perhaps lucreate dislikes being run with sudo.
> 
> The problem I'm now seeing is that the cifs server will happily offer
> up this share (and one other that's doing the same thing), but no
> files appear in it.  Other shares from the same zpool work fine.  I'm
> actually even able to write to these two broken shares, but files that
> I add to them still don't show up to smb clients.  Very odd.  It's
> like what I would expect to see if the directories lacked the execute
> bit, but that's not the case - one broken share is mode 755 and owned
> by me, and the other is mode 1777.
> 
> I've tried "zfs set sharesmb=off" and back on for the affected shares,
> and I see the problem from several different clients, not just one.
> What should I try next?
> 
> Thanks,
> 
> - Ben
> _______________________________________________
> cifs-discuss mailing list
> cifs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/cifs-discuss