similar to: Samba 4 Alpha 17 to 4.0.x update - questions concerning S3FS / NTVFS

Hi, how can I what filer server is currently running in samba4, s3fs or ntvfs? My smb.conf looks like this: server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind, ntp_signd, kcc, dnsupdate, web dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, backupkey, dnsserver Im asking as when looging

I've noticed that the samba-tool ntacl sysvolreset --use-s3fs command does not work on a ZFS filesystem on FreeBSD. It does work if sysvol is moved to a volume that is able to be mounted with the acls flag. I will reference a ticket I started with FreeNAS here: https://bugs.freenas.org/issues/4351 As of version 9.2.1.1 s3fs is now the default using the workaround known for FreeBSD.

On Mon, 05 Dec 2016 21:30:20 +1300 Andrew Bartlett <abartlet at samba.org> wrote: > On Mon, 2016-12-05 at 08:12 +0000, Rowland Penny via samba wrote: > > On Mon, 05 Dec 2016 21:07:48 +1300 > > Andrew Bartlett <abartlet at samba.org> wrote: > > > > > > > > > > > > > It is a lot of work to change the situation, even more so

Reading Whatsnew.txt in samba I understand that If I use s3fs, as it is set by default in the provision step, I won't be able to modify GPOs later, right? So I have a couple of questions: - What's the advantage of using s3fs over ntvfs in new installations? - If I'm planning to deploy a new Domain, probably needing to change GPOs later, should I select ntvfs??? Best regards, Felix

On Mon, 05 Dec 2016 21:07:48 +1300 Andrew Bartlett <abartlet at samba.org> wrote: > > It is a lot of work to change the situation, even more so without loss > of important tests.  A number of tests, particularly for spoolss but > also of the cifs proxy (which in turn tests kerberos delegation), use > the ntvfs file server. OK, but how can you be sure that something you are

Hello! I've just built my first samba4 (4.0.5) on an OpenIndiana machine without any problems. But when it comes to the provision step the problems begin. Everything is fine, if I call samba-tool with the --use-ntvfs option. But I want to use samba4 with s3fs because of the support for newer SMB protocol versions. But when I call samba-tool without --use-ntvfs option I got the following:

Hello, I'm trying to configure a CIFS-Proxy. My configuration is: [global] workgroup = MYDOM server role = member server realm = MYDOM.NET netbios name = FS01 server services = +smb +s3fs dcerpc endpoint servers = +winreg +srvsvc [test] ntvfs handler = cifs cifs:server = 192.168.1.10 cifs:share = projects$ but in

In samba-tool, sysvolreset has options for either --use-ntvfs or --use-s3fs to set the permissions appropriately However, sysvolcheck does not have the same capability, and always attempts to verify in s3 vfs. Is this a known limitation in Samba 4.0.0 ?

Hi all, I am in the process of finding the best way to use Samba4 as an AD under FreeBSD and ZFS. The following is based on own research, google, mail archives, a bit of source code etc. So please correct me if I am wrong. 1. ZFS is using NFSv4 ACLs. 2. NFSv4 ACLs are modelled with NTFS (Windows) ACLs in mind. 3. Samba4 started with a new ntvfs file server but that was abandoned (or

I have an existing install of Samba4 ( I think beta6 vintage ), which uses ntvfs and bind9. It's only providing AD and Group Policy. I have a seperate file server running 3.6.x. I want to add a server to the domain running the most recent RC. I know they are using internal by default and s3fs for the file shares on sysvol. Can s3fs coexist with ntvfs? Can the internal DNS coexist with

Hi How about calling s3fs, s4fs? Cheers, Steve

On Fri, 2 Sep 2016 13:03:05 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 2 Sep 2016 12:41:47 +0100 > Cameron Murdoch via samba <samba at lists.samba.org> wrote: > > > On 2 September 2016 at 12:21, Rowland Penny via samba > > <samba at lists.samba.org > > > wrote: > > > > > On Fri, 2 Sep 2016 11:51:02 +0100

On 2 September 2016 at 12:21, Rowland Penny via samba <samba at lists.samba.org > wrote: > On Fri, 2 Sep 2016 11:51:02 +0100 > Cameron Murdoch <cam at macaroon.net> wrote: > > > On 2 September 2016 at 09:53, Rowland Penny via samba > > <samba at lists.samba.org > > > wrote: > > > > > On Thu, 1 Sep 2016 14:12:21 +0100 > > >

Hi, I am trying to create a build on CircleCi with smaba4 AD. It seems the filesytem doesn't support ACL's, which s3fs requires. I get the folowing error: ?ERROR(<class 'samba.provision.ProvisioningError'>): Provision failed - ProvisioningError: Your filesystem or build does not support posix ACLs, which s3fs requires.? Try the mounting the filesystem with the

We are proud to a announce another alpha release of Samba 4.0, alpha 21 What's new in Samba 4 alpha21 ============================= Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4 alpha series and the stable 3.x series. The primary additional features over Samba 3.6 are support for the Active Directory logon protocols used by

On Mon, 05 Dec 2016 07:50:23 +1300 Andrew Bartlett <abartlet at samba.org> wrote: > On Sun, 2016-12-04 at 11:43 +0000, Rowland Penny via samba wrote: > > On Sun, 4 Dec 2016 12:11:17 +0100 > > Marc Muehlfeld via samba <samba at lists.samba.org> wrote: > > > > > > > > Hi Scott, > > > > > > Am 02.12.2016 um 06:55 schrieb Scott

On Mon, 2016-12-05 at 08:47 +0000, Rowland Penny via samba wrote: > On Mon, 05 Dec 2016 21:30:20 +1300 > Andrew Bartlett <abartlet at samba.org> wrote: > > > > > On Mon, 2016-12-05 at 08:12 +0000, Rowland Penny via samba wrote: > > > > > > On Mon, 05 Dec 2016 21:07:48 +1300 > > > Andrew Bartlett <abartlet at samba.org> wrote: > >

Hi! I have updated our server from Samba 4 alpha 17 to Samba 4.0.1. Everything seems to work fine after some reconfiguration, but our GPOs are not working anymore. Samba 4 alpha 17 was using ntvfs and the root partition with the sysvol share was mounted with "user_xattr" only in /etc/fstab. Samba 4.0.1 is now set to use s3fs and the root partition is mouted with

Hi Everybody, I'm stumped. I'm pretty sure I've tried everything to get this to work. I'm trying to join my CentOS 6 server to my Server 2008 AD Domain. I'm using SerNet's samba4 packages: [root at files ~]# samba -V Version 4.1.4-SerNet-RedHat-7.el6 I've done the xattr and acl tests and they all come out just fine. So I don't think it has to do with ACLs

Release Announcements --------------------- This is the fourth release candidate of Samba 4.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4