![]() Vdev-0 = 4 x 6 TB drives in RAID-z1 (4 WD Gold drives - WD6002FRYZ) Vdev-1 = 6 x 4 TB drives in RAID-z2 (6 Seagate Exos drives - ST4000NM0115) Vdev-0 = 6 x 4 TB drives in RAID-z2 (6 Seagate Exos drives - ST4000NM0115) Vdev-1 = 6 x 4 TB drives in RAID-z2 (6 Seagate Desktop drives - ST4000DM000-1F2168) Vdev-0 = 6 x 4 TB drives in RAID-z2 (6 Seagate Desktop drives - ST4000DM000-1F2168) HBA: LSI/Broadcom SAS9207-8i, 6Gbps SAS PCI-E 3.0 HBA - flashed to IT Firmware: 20.00.07.00Ĭonnected to: two 6Gb/s 24-port 3.5" mini-SAS expander backplanes (80H10024001A0) 128 GB of 16GB sticks Samsung brand PC3-12800R, DDR3 Registered ECC Processor: Intel Xeon E5-2650 V2, 2.6GHz 8 Core (16 thread) System board: SuperMicro Motherboard X9SRL-F, LGA 2011/Socket R, IPMI For a home NAS, this chassis is huge, able to hold 48 data drives and two boot drives with a couple spaces internally for non-hot-swap drives. The three pools in this one system represent the three NAS systems I had before the consolidation. I have even put together some hardware just to test things out a time or two.įor a while I had three systems, all at once, at home but I am making some hardware changes right now and only one NAS is online. I made some mistakes along the way, learned some and I try to share some of those lessons learned experiences here in the forum. This is the 8th FreeNAS unit I have built for home. This one was built in 2018, but I reused the name from a previous build. I just superstitiously follow my above practice, and that is my personal contribution to the vast amounts of samba voodoo that floats around the internet. # group: NEWCONTOSO\domain in short, I don't have a good explanation for the behavior you describe above, it is not clear whether it adversely affects FreeNAS performance, and I'm not sure what the remedy would be. I try also to avoid limiting rights of the owner and group (in some hard-to-pin-down situations this can lead to samba on FreeNAS arbitrarily writing "deny" ACEs).Īnyway, you if you make the changes I mention above, your getfacl output should /mnt/volume# getfacl pollaio/ In general I try to avoid making or using groups that share a name with a user, and vice-versa. The behavior you described also annoyed me a bit and so I changed ownership of my datasets to "root:domain admins". I believe "administrator" is both a user and a Builtin Container (see output of getent group). I think a part of the problem may be with using the parameter "nfs4:mode = special". Thank's in advice for the help and please excuse any mistakes as English is my second language.Ĭlick to expand.I've noticed that winbind/ zfsacl can get confused if you have users and groups with identical names. Group:NEWCONTOSO\administrator:rwxpDdaARWcCo-:fd-:allow Group:NEWCONTOSO\fattoria_mckenzie:rwxp-daARWc-:fd-:allow View attachment /mnt/volume# getfacl pollaio/ I've made a test lab for simulating the problem here's an example : This is my first time in the forum, because i use without problem FreeNas from version 8 (and before version 7) as NAS for exporting CIFS Shared Folder in a Windows Environment binded sometimes with a Samba Active Directory (Resara) or Windows Server DC.Īfter i've upgraded one of the box to FreeNAS 9.3, i've noticed that if I set the permission of a folder from Windows, giving ad example the Full Control permission to the DOMAIN\Administrator user, when i use the getfacl command on the freenas box i retrieve that DOMAIN\Administrator is viewed as group.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |