similar to: NFS4 ACLs with samba 3 (or 4)

> Date: Thu, 19 Mar 2015 11:59:47 +0100 > From: Volker.Lendecke at SerNet.DE > To: groucho.64738 at hotmail.com > CC: samba at lists.samba.org > Subject: Re: [Samba] NFS4 ACLs with samba 3 (or 4) > > On Wed, Mar 18, 2015 at 01:17:34PM -0400, Kevin Taylor wrote: > > I know this was discussed a lot a few years ago, but my google searches aren't quite getting me where

> On Dec 3, 2015, at 17:24, Jeremy Allison <jra at samba.org> wrote: > >> On Thu, Dec 03, 2015 at 03:54:21PM -0700, Nick Couchman wrote: >> I have a situation where I need to share, via Samba, a filesystem mounted via NFSv4. I'm struggling with the best way to make Samba see the NFSv4 ACLs and enumerate them to provide the proper SMB/CIFS access to the files, instead

> Date: Thu, 19 Mar 2015 11:59:47 +0100 > From: Volker.Lendecke at SerNet.DE > To: groucho.64738 at hotmail.com > CC: samba at lists.samba.org > Subject: Re: [Samba] NFS4 ACLs with samba 3 (or 4) > > On Wed, Mar 18, 2015 at 01:17:34PM -0400, Kevin Taylor wrote: > > I know this was discussed a lot a few years ago, but my google searches aren't quite getting me where

I have a situation where I need to share, via Samba, a filesystem mounted via NFSv4. I'm struggling with the best way to make Samba see the NFSv4 ACLs and enumerate them to provide the proper SMB/CIFS access to the files, instead of "Access Denied" errors that I currently get. Looking at the Samba source, the only obvious NFSv4 stuff appears to be the following: - zfsacl, available

On Wed, Mar 18, 2015 at 01:17:34PM -0400, Kevin Taylor wrote: > I know this was discussed a lot a few years ago, but my google searches aren't quite getting me where I'm confident in the answer, so I figure I'd just ask again here if that's ok. > > Here's what we have, and what we'd like to do: > > Storage is a Netapp (cluster mode CDOT 8.2 I believe),

----- Original Message ----- > From: "Jeremy Allison" <jra at samba.org> > To: "Nick E Couchman" <nick.couchman at seakr.com> > Cc: samba at lists.samba.org > Sent: Thursday, December 3, 2015 6:13:51 PM > Subject: Re: [Samba] Linux & NFSv4 ACLs > On Thu, Dec 03, 2015 at 06:03:39PM -0700, Nick Couchman wrote: >> >> > On Dec 3,

I have an NFS4 server exporting a folder, and a Samba server importing that folder which it then turns around and shares over Samba. I would like Windows machines accessing this folder and its sub folders to be properly restricted according to ACLs. The NFS4 server is running CentOS 5.7 and is NFS exporting an EXT4 folder. The Samba server is running CentOS 6.0, and Samba 3.5.4-68.el6_0.2. On the

Am 19.03.2015 um 17:39 schrieb Jeremy Allison: > On Thu, Mar 19, 2015 at 10:16:20AM -0400, Kevin Taylor wrote: > >> Unfortunately I'm not a programmer, so I don't know if there is an API or not. As far as me the user can tell is that we have an NFSv4 filesystem mounted on the linux box. We have tools available through the nfs4-acl-tools package (this is on CentOS 6, for

Hai..   I need to have my home dirs shared over some of my servers. I did setup a nfs4 kerberos base Debian jessie, samba 4.1.17 and sernet samba 4.1.3 on these servers.   This works, i can mount without problems.   But because verything is created with the windows user tools, the owner/Group is root. Like this   Server:   ls -al drwxrwx---+  2 root  root 4096 Sep  4 13:17

Am 20.03.2015 um 10:45 schrieb Volker Lendecke: > On Thu, Mar 19, 2015 at 05:47:11PM +0100, Robert Schetterer wrote: >>> Well the API is propably just stuffing blobs into extended >>> attributes directly from userspace. That's how most of >>> the NFSv4 ACLs usually get done :-(. >>> >>> Of course all implementations use different blobs containing

Hi, We are running into a problem with a Samba setup and would like to know if a current fix or workaround is at all possible. Our setup is a NetApp filer serving NFS v4 that is mounted by Solaris and Linux servers. On those servers we are using Samba to create shares of those NFSv4 mounted filesystems. We are migrating to this NFSv4 setup from an existing Solaris NFSv3+Posix ACL setup that also

On Fri, Apr 06, 2018 at 10:27:32AM -0700, Jeremy Allison via samba wrote: > On Fri, Apr 06, 2018 at 01:44:50PM +0530, Akash Jain wrote: > > Hi All > > > > I found there is one bug in the plugin. The name of the attribute for ACL as > > per strace output of nfs4_setfacl is system.nfs4_acl. > > The source code has defined it as > > #define

----- Original Message ----- > From: "Jeremy Allison" <jra at samba.org> > To: "Nick E Couchman" <nick.couchman at seakr.com> > Cc: samba at lists.samba.org > Sent: Friday, December 4, 2015 1:22:06 PM > Subject: Re: [Samba] Linux & NFSv4 ACLs > On Thu, Dec 03, 2015 at 07:31:36PM -0700, Nick Couchman wrote: >> >> Try these pages (U

Hi everyone, I'm sorry if this has already been covered somewhere, but I've had a look and can't find it. Also if there is a better place for this question, please let me know. I know that the CTDB documentation states that only NFS2/3 are supported with CTDB but what I'd really like to know is why NFS4 won't work and if NFS4 support is planned for the future (timeline?).

Hi All I found there is one bug in the plugin. The name of the attribute for ACL as per strace output of nfs4_setfacl is *system.nfs4_acl.* The source code has defined it as #define NFS4ACL_XATTR_NAME ( "system.nfs4acl" ) Note there is missing underscore. After this, the EOPNOTSUPP error is not observed. Hope this helps Akash On Thu, Apr 5, 2018 at 11:43 PM, Jeremy Allison

On Fri, Apr 06, 2018 at 12:40:31PM -0700, Jeremy Allison wrote: > On Fri, Apr 06, 2018 at 09:22:17PM +0200, Ralph Böhme wrote: > > On Fri, Apr 06, 2018 at 10:27:32AM -0700, Jeremy Allison via samba wrote: > > > On Fri, Apr 06, 2018 at 01:44:50PM +0530, Akash Jain wrote: > > > > Hi All > > > > > > > > I found there is one bug in the plugin. The

Hello, I am searching for a solution that I thought should be kind of standard, but until now I was not successful finding anything. Here is the problem: At our site we offer windows and linux, most servers (eg file, samba, web) are linux based. User data is stored on NFS file servers. Windows systems are part of a Windows domain with an ADS domain controller. At the moment the linux samba

Is idmapd supposed to work where users have different uid numbers on the nfsv4 server and client? It seems to show the right names for ownership on the client side, but if I automount a home directory, that user doesn't have permission to enter it, and if I change permission to allow access and create a new file, it shows on the server as owned by the uid number for the user on the client

just a quick update: no issues with NFSv4.0 (load is slowly growing, currently ~7k mailboxes) instead, bad news from delegation front, we enabled it for a couple of days but we ran in ugly issues: processes went in "uninterruptible sleep" state, load average gets huge, reboot was the only escape :-( -brd Alessio Cecchi wrote: > Il 12/06/2015 13:02, brd ha scritto: > >Alessio

Alessio Cecchi wrote: [...] > Have you already try to run NFSv4? it's in place on a (very) small sample of mailboxes in dbox format, no issues up to now (Debian Wheezy mainline kernel) > When we switch to netapp and nfsv4 we had many problems (lock problems > and instability) and we had to go immediately to NFSv3. I don't know if > was a netapp problem or nfs client (Debian