similar to: aclinherit property changes fast track

I am running a test system with Solaris 10u6 and I am somewhat confused as to how ACE inheritance works. I''ve read through http://opensolaris.org/os/community/zfs/docs/zfsadmin.pdf but it doesn''t seem to cover what I am experiencing. The ZFS file system that I am working on has both aclmode and aclinherit set to passthrough, which I thought would result in the ACEs being just

I have OSol 2009.06 (b111a), and I''m not sure I''m getting this ZFS ACL thing: %whoami abalfour % ls -V file ----------+ 1 abalfour root 1474560 May 11 18:43 file owner@:-w--d--A-W-C--:-------:deny according to that ACL I shouldn''t be able to write anything having to do with file, correct? % cat >> file zsh: permission denied: file % mv file

Hi list, while preparing for the changed ACL/mode_t mapping semantics coming with onnv-147 [1], I discovered that in onnv-134 on my system ACLs are not inherited when aclmode is set to passthrough for the filesystem. This very much puzzles me. Example: $ uname -a SunOS os 5.11 snv_134 i86pc i386 i86pc $ pwd /Volumes/ACLs/dir1 $ zfs list | grep /Volumes rpool/Volumes 7,00G 39,7G 6,84G

Hi all, I'd appreciate any pointers or advise regarding the following issue with files written by M$ Office on Samba 3.0.32 on snv_98 (OpenSolaris) on a ZFS filesystem: samba share: [sharename] read only = No browseable = yes writeable = yes directory mask = 0770 create mask = 0770 delete readonly = Yes acl check permissions =

Hello forum. I''m in the process of re-organizing my server and ACL-settings. I''ve seen so many different ways of doing ACL, which makes me wonder how I should do it myself. This is obviously the easiest way, only describing the positive permissions: /usr/bin/chmod -R A=\ group:sa:full_set:fd:allow,\ group:vk:read_set:fd:allow \ However, I''ve seen people split each

I figured the following ZFS ''success story'' may interest some readers here. I was interested to see how much sequential read/write performance it would be possible to obtain from ZFS running on commodity hardware with modern features such as PCI-E busses, SATA disks, well-designed SATA controllers (AHCI, SiI3132/SiI3124). So I made this experiment of building a fileserver by

Hi, I tried again with some other options. After finding http://www.dovecot.org/list/dovecot/2013-November/093793.html I deleted every ACL from the directory Maildir and I also assigned the group "mail" to it, recursively: OmniOS-Xeon:/tank/home/olaf/Maildir/.Generiche $ ls -lV total 903 drwxrwxrwx 2 olaf mail 2 Sep 27 23:47 cur

I''m currently prototyping a Solaris file server that will dish out user home directories and group project directories via NFSv4 and Samba. I have samba configured and integrated into our local active directory, with ACL mapping working. I''m a little confused as to the behavior of the ZFS ACL though. on a brand-new filesystem, touching a file results in: -rw-r--r-- 1 root

Trying to boot my Thinkpad T30 with Solaris snv_81 xVM it get the error message This version of Solaris xVM does not support this hardware The output of "echo ::interrupts | mdb -k" while booted without xVM is bash-3.2# echo ::interrupts | mdb -k IRQ Vector IPL(lo/hi) Bus Share ISR(s) 0 0x20 14/14 - 1 cbe_fire 1 0x21 5/5 ISA 1 i8042_intr 3 0x23

Dear Dovecot users, hello. I will merge two issues I have into a single email because they may be related. I used dovecot on a OmniOS server since 2014 (currently OmniOS r151014) with the following configuration (it shows 2.2.18 because I recently updated dovecot, skipping only the PostgreSQL plugin): # 2.2.18: /etc/dovecot/dovecot.conf # OS: SunOS 5.11 i86pc zfs mail_location =

Hi, this says that opensolaris only requires 512MB ram: http://dlc.sun.com/osol/docs/content/IPS/sysreq.html This says 1GB ram and a 64bit processor are recommended: http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide#Memory_and_Swap_Space Am I going to have problems if I run opensolaris and zfs at the minimum requirements? -- This message posted from opensolaris.org

The time has come to review the current Contributor and Core contributor grants for ZFS. Since all of the ZFS core contributors grants are set to expire on 02-24-2009 we need to renew the members that are still contributing at core contributor levels. We should also add some new members to both Contributor and Core contributor levels. First the current list of Core contributors: Bill

Hi, S10U3: It seems, that ufs POSIX-ACLs are not properly translated to zfs ACL4 entries, when one xfers a directory tree from UFS to ZFS. Test case: Assuming one has an user A and B, both belonging to group G and having their umask set to 022: 1) On UFS - as user A do: mkdir /dir chmod 0775 /dir setfacl -m d:u::rwx,d:g::rwx,d:o:r-x,d:m:rwx /dir # samba would

https://bugzilla.samba.org/show_bug.cgi?id=8948 Summary: ZFS acls are not inherited. Product: rsync Version: 3.0.9 Platform: All OS/Version: Solaris Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: ryan at mailinator.com

Hi all, Running samba 3.5.5 in a Solaris non-global zone. I have created a folder (StudentJobApplications) on a share which I want to make accessible only to members of a Unix group (studempl). I have added myself to the group but when I or other group members try to access the folder via Windows Explorer I get the following: I:\StudentJobApplications is not accessible Access is denied Here

Hi @all, with ZFS its recommended to create a new filesystem, for example for each user to give them a home directory. So far, so good. The homes should be under tank/export/home/staff and my intention is to restrict the ACL rights so only the user self can access his own home directory. I study the ZFS Admin Guide and found the aclmode and aclinherit options, IMHO for my intention the

Hi, Just playing with zfs and the admin manual ... # mkfile 100m /export/zfs/disk1 # zpool create data /export/zfs/disk1 # zfs create data/users # zfs mount -o remount,noatime data/users # zfs get all data/users NAME PROPERTY VALUE SOURCE data/users type filesystem - data/users creation Mon Nov 20 11:25 2006

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

I have a weekly scrub setup, and I''ve seen at least once now where it says "don''t snapshot while scrubbing" Is this a data integrity issue, or will it make one or both of the processes take longer? Thanks

As part of looking into a minor issue with the group listed when using runat(1) on a UFS filesystem for Johannes (my Google Summer of Code student work on new basic file privs), I discovered an even bigger issue with UFS and extended attributes. I''ve cc''d ZFS discuss because I used ZFS as the comparison and I believe that ZFS is acting correctly but even then it might not be