zfs discuss - Feb 2010 - acl''s and new dirs

I''ve got a strange issue,  If this is covered elsewhere, i apologize in
advance for my newbness

I''ve got a couple ZFS filesystems shared cifs and nfs, i''ve
managed to get
ACL''s working the way i want, provided things are accessed via cifs and
nfs.

If i create a new dir via cifs or NFS then the acl''s work exactly as i
want,
but if i do the same thing with shell using mkdir, it
doesn''t.....i''m not
sure what i''m missing here...

basically,  if i create the dir with mkdir, it creates, it looks ok but i
can''t copy files into it.....why should this be?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100206/d831d8d3/attachment.html>

Thomas Burgess wrote:
> I''ve got a strange issue,  If this is covered elsewhere, i
apologize in
> advance for my newbness
> 
> I''ve got a couple ZFS filesystems shared cifs and nfs,
i''ve managed to
> get ACL''s working the way i want, provided things are accessed via
cifs
> and nfs.
> 
> If i create a new dir via cifs or NFS then the acl''s work exactly
as i
> want, but if i do the same thing with shell using mkdir, it 
> doesn''t.....i''m not sure what i''m missing
here...
> 
What is the ACL on the parent directory?

What are the settings of the aclinherit and aclmode properties?

How are you creating the directory?  Is it /usr/bin/mkdir or 
/usr/gnu/bin/mkdir?
> basically,  if i create the dir with mkdir, it creates, it looks ok but 
> i can''t copy files into it.....why should this be?
> 
That doesn''t make sense, NFS and local should access should behave the 
same way.

The CIFS serve bypasses the aclmode/aclinherit properties and always 
creates files/dir with strict windows ACL inheritance semantics.