search for: write_xattr

...the parent directory; files within have the same permissions (sans the inheritance). moe-lh /moe2/office/student_workers 546# ls -vd . drwxrws---+ 2 toml cefac 5 Oct 20 18:36 ./ 0:group:cefac:list_directory/read_data/add_file/write_data /add_subdirectory/append_data/write_xattr/execute/write_attributes /write_acl/write_owner:file_inherit/dir_inherit/inherit_only:allow 1:group:cefac:list_directory/read_data/add_file/write_data /add_subdirectory/append_data/write_xattr/execute/write_attributes /write_acl/write_owner:allow 2:group:ce...

...ls -V I only have owner and group ACLs...nothing for everyone. bash-3.00$ id uid=100(timt) gid=10001(ccbcadmins) bash-3.00$ groups ccbcadmins staff bash-3.00$ ls -v testacl -rwxrwx---+ 1 timt ccbcadmins 0 Jan 31 16:24 testacl 0:owner@:read_data/write_data/append_data/read_xattr/write_xattr/execute /delete_child/read_attributes/write_attributes/delete/read_acl /write_acl/write_owner/synchronize:allow 1:group@:read_data/write_data/append_data/read_xattr/write_xattr/execute /delete_child/read_attributes/write_attributes/delete/read_acl /wri...

...issions shown. In windows it looks fine, and under Solaris it looks ok too, the permissions appear as: d---r-x---+ 3 ross smith domain users 3 Feb 28 08:24 Departments 0:group:domain admins:list_directory/read_data/add_file/write_data /add_subdirectory/append_data/read_xattr/write_xattr/execute /delete_child/read_attributes/write_attributes/delete/read_acl /write_acl/write_owner/synchronize:file_inherit/dir_inherit:allow 1:group@:list_directory/read_data/read_xattr/execute/read_attributes /read_acl/synchronize:file_inherit/dir_inherit:allow However, if I log...

...wxrwx---+ 13 jsmith sales 48 Nov 29 18:58 /Pool1/Department/Sales 0:user:nobody:read_xattr/read_attributes/read_acl:allow 1:user:root:read_xattr/read_attributes/read_acl:allow 2:group@:list_directory/read_data/add_file/write_data/add_subdirectory /append_data/read_xattr/write_xattr/execute/delete_child /read_attributes/write_attributes/delete/read_acl/write_acl /write_owner/synchronize:allow 3:owner@:list_directory/read_data/add_file/write_data/add_subdirectory /append_data/read_xattr/write_xattr/execute/delete_child /read_attributes/write_attributes/delete/read_acl...

There are definitely some files with some weird names- in an ssh session they don't even have regular characters. e.g -rw-rw---- 1 xxx xxx 114985112 Oct 31 14:39 ▒^t Not sure if that is related to problems though. The top command shows Memory: 12G phys mem, 343M free mem, 2048M total swap, 2048M free swap This is in the evening so should not be much load but I think

ZFS introduces a new and incompatible ACL interface into Solaris and this seems to be not yet fully completed in addition to the fact that is causes a lot of problems for software that needs to be compatible with Solaris-2.5 like star. Proof for incompatibility: create a file on UFS and set an ACL for this file. Use Sun tar cpf out file to archive this file. Unpack this archive file on ZFS

..." (euid = 35661, syscall = 224) needed at ufs_iaccess+0xf8 cp: cannot create attr.1: Permission denied Hmn, slightly strange since I would have thought that given write to the file I could write attributes. ZFS is consistent in this because the default ZFS ACL does not have everyone@ having write_xattr. Maybe not quite what one would expect. Okay now in another window change the ownership of this world writable file to darrenm islay:pts/4$ runat test3 cp /tmp/attrdata attr.1 cp[1802]: missing privilege "ALL" (euid = 35661, syscall = 224) needed at ufs_iaccess+0xf8 cp: cannot creat...

...tion ================= No specific workgroup No AD or LDAP configuration Acls on folder bigmirror/big: local users smb and nfs, owner@ have full access, everyone@ and group@ (root) are denied write access owner@ Allow:list_directory, read_data, add_file, write_data, add_subdirectory, append_data, write_xattr, execute, write_attributes, write_acl, write_owner group@ Allow:list_directory, read_data, execute Deny:add_file, write_data, add_subdirectory, append_data everyone@ Allow:list_directory, read_data, read_xattr, execute, read_attributes, read_acl, synchronize Deny:add_file, write_da...

...ffective:rwx 2:mask:rwx 3:other:r-x -bash-3.00# ls -lavd /zfs/internal/streams drwxrwsr-x 2 root NDS-UK\dept_stream_content 3 Jan 18 14:38 /zfs/internal/streams/ 0:owner@::deny 1:owner@:list_directory/read_data/add_file/write_data/add_subdirectory /append_data/write_xattr/execute/write_attributes/write_acl /write_owner:allow 2:group@::deny 3:group@:list_directory/read_data/add_file/write_data/add_subdirectory /append_data/execute:allow 4:everyone@:add_file/write_data/add_subdirectory/append_data/write_xattr /write_attributes/write...

...-a-R-c--s:------:allow There is also a "verbose" format, similar - but not identical - to the SunOS counterpart: [trasz@traszkan:~]$ getfacl -v / # file: / # owner: root # group: wheel owner@:::deny owner@:read_data/write_data/execute/append_data/write_attributes/write_xattr/write_acl/write_owner::allow group@:write_data/append_data::deny group@:read_data/execute::allow everyone@:write_data/append_data/write_attributes/write_xattr/write_acl/write_owner::deny everyone@:read_data/execute/read_attributes/read_xattr/read_acl/synchr...

...that happen with a normal chmod except for the write_acl part. It looks like this: chown root username chmod A- username chmod og-rwx username chmod A+user:username:write_acl:deny username chmod A+user:username:list_directory/read_data/add_file/write_data/add_subdirectory/append_data/read_xattr/write_xattr/execute/delete_child/read_attributes/read_acl/write_owner/synchronize:allow username chmod A+group@:read_xattr/read_attributes/read_acl/synchronize:allow username chmod A+everyone@:read_xattr/read_attributes/read_acl/synchronize:allow username This all works very well when using an NFS mounted fil...

After a crash, in my zpool tree, some dataset report this we i do a ls -la: brwxrwxrwx 2 777 root 0, 0 Oct 18 2009 mail-cts also if i set zfs set mountpoint=legacy dataset and then i mount the dataset to other location before the directory tree was only : dataset - vdisk.raw The file was a backing device of a Xen VM, but i cannot access the directory structure of this dataset. However i