similar to: Solaris 10, zfs and windows

I am looking for where zfsacl settings such as, zfsacl: acesort = dontcare , are documented. Do I need NFS settings such as, nfs4: mode = simple , if I am not using NFS? If I do, where are they documented? Thanks

Hi, When samba is joined to a 2k3 domain, UPN authentication does not work. It works using smbclient, but not from a workstation that is not part of the domain. I can reproduce this easily and provide logs and tcpdump's if necessary. The same problem does not occur when samba is joined to 2k8 or 2k12 domains. Is this by design? Am I missing something? - John -------------- next part

On 17/02/16 17:27, Ian wrote: > > On 2/17/2016 5:00 AM, Rowland penny wrote: >> On 17/02/16 00:03, Ian wrote: >>> I've recently attempted to migrate some windows server files over to >>> samba 4 hosted on a FreeNAS server. >>> >>> Using robocopy with the /copyall switch, I expected everything, >>> including ACL's and ownership

Hello, I am unable to change ownership of Samba shares on Windows. It makes no difference if Samba is a PDC or if it is a member server in an Active Directory. I am running Samba 4.1.9 on FreeBSD 9.2 with ZFS. I can easily change ownership locally on the FreeBSD box, however, when trying to do it from Windows it errors out with access is denied. I've attempted to use net rpc rights grant

On 2/17/2016 9:43 AM, Rowland penny wrote: > On 17/02/16 17:27, Ian wrote: >> >> On 2/17/2016 5:00 AM, Rowland penny wrote: >>> On 17/02/16 00:03, Ian wrote: >>>> I've recently attempted to migrate some windows server files over to >>>> samba 4 hosted on a FreeNAS server. >>>> >>>> Using robocopy with the /copyall switch,

I'm seeing some really poor performance out of my FreeNAS (ver 9.10) machine, running Samba "4.3.6-GIT-UNKNOWN". I'm using IOMeter to benchmark sequential reads, and getting around 35-40 MB/sec, which seems unusual. Mostly, I'm hoping someone can point me in the direction of a decent tuning guide for a SOHO machine running Samba, but if you're inclined, I'll delve

On 2/17/2016 5:00 AM, Rowland penny wrote: > On 17/02/16 00:03, Ian wrote: >> I've recently attempted to migrate some windows server files over to >> samba 4 hosted on a FreeNAS server. >> >> Using robocopy with the /copyall switch, I expected everything, >> including ACL's and ownership information to transfer over. For the >> most part they have.

This is the samba conf file (not on the DC's, but on the box where profiles are being stored - which is where our problem is, IMO) - does anything in here need addressing? [I've slightly sanitized some names.] I'm trying to gather relevant samba logs from this same box, as well as anything that looks relevant from the Windows station event logs. But I thought starting here might be

Hi. I'm using Samba on FreeBSD to host various file servers. Recently I've noticed one weird thing: samba needs w flag on file for being able to delete it, plus, when 'force user' is used, samba needs additional flags for group owning the file. Not sure if it was there all the time and it's just me, or may be this is an intended behaviour (I hope not), so, anyway I'll

All, Running Samba 3.5.4 on Solaris 10 with ZFS file system. I have issues where we have shared group folders. In these folders a userA in GroupA create file just fine with the correct inherited permissions 660. Problem is when userB in GroupA reads and modifies that file, with M$ office apps, the permissions get whacked to 060+ and the file becomes read only by everyone. I did

My Server is running 4.5.1 on Ubuntu 16.04, most of the shares are located on a zfs raid. Some of the added profiles are now getting corrputed and cannot login anymore due to some files in the profile share not being accessible After searching online I found two solutions: a) setting aclmode=passthrough, aclinherit=passthrough on the zfs volume b) using nt4 acl mode and the vfs_zfsacl module on

I'm trying to learn more about samba by experimenting with samba on FreeNAS. This involves a certain amount of reading how default smb4.conf parameters are set in FreeNAS and then reading the manpages for those parameters. Async I/O is implemented in samba in freenas via the aio_pthread VFS module. The manpage for vfs_aio_pthread states: "the smb.conf parameters aio read size and aio

Hi It seems the vfs objects are not loaded. I've joined the domain with "samba-tool domain join DOMAIN DC -UAdministrator%Passwort --realm=DOMAIN.LOCAL --server=windows-dc.domain.local --use-ntvfs" The modules zfsacl.so and recycle.so exists in /usr/local/lib/shared-modules/vfs But neither the ZFS module nor the recycler works. Samba version: 4.0.13 Build host: FreeBSD

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

I'm running the latest FreeBSD 10.0-CURRENT with samba 3.6.5. I'm sharing some folders from a ZFS file system properties of the zfs filesystem: tank/users aclmode passthrough inherited from tank tank/users aclinherit passthrough received When I create a file via a windows client on the shared volume following ACL is applied: getfacl

I'm trying to use zfs acls in solaris 10. I've looked at past posts regarding this and some online help, but am stuck. I'm currently using samba 3.3.9; I've had the same problem with 3.3.7. samba is compiled and running as an Active Directory member server (compiled with ldap and kerberos). The zfs disk is local. I'm not using winbind. I compiled with zfsacl module.

I'm running Samba 4.7.0 on FreeNAS 11.1-U2. It's configured as an Active Directory Domain Controller, and I'm trying to configure roaming profiles. I've created a profile dataset in ZFS that uses Windows permissions. I've configured the share and file system permissions as described in the "Using Windows ACLs" section of:

Hi, I have an NFS mount point served as a samba share. I know it's kind of lame, and until recenlty I was sure that this isn't the kind of case that would work, because over the years I experimented with this and all I was getting were failures. But I accudentally discovered that it's working, but under one condition: the user must be a domain administrator (my samba is a AD

I recently upgrade an older version of Samba (3.x) to a less older version of Samba (4.4.8) and now have users reporting the following error. There is not enough disk space on home (servername). You need an additional XXX to copy these files. I see some older posts referring to adjusting, *min receivefile size = * *0, *however I do not have this set and the default is 0. I don't see

On Wed, 8 Feb 2017 16:43:53 -0600 Paul Klapperich via samba <samba at lists.samba.org> wrote: > Very well. Here is the affected smb.conf. > ------ > [global] > server min protocol = NT1 > server max protocol = SMB3 > interfaces = 127.0.0.1 10.0.0.8 > bind interfaces only = yes > encrypt passwords = yes > dns proxy = no > strict