From: "Björn JACKE" <bjacke@SerNet.DE>
To: Jeremy Allison <jra@samba.org>
Cc: Michael Weiser <michael.weiser@atos.net>,
"samba@lists.samba.org" <samba@lists.samba.org>,
Daniel Kobras <kobras@puzzle-itc.de>,
"lustre-discuss@lists.lustre.org"
<lustre-discuss@lists.lustre.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [Samba] [lustre-discuss] Odd "File exists" behavior when copy-pasting many files to an SMB exported Lustre FS
Date: Fri, 23 Sep 2022 19:53:55 +0200 [thread overview]
Message-ID: <20220923175354.GA574247@sernet.de> (raw)
In-Reply-To: <YyyPfX7J2LKEI4QG@jeremy-acer>
On 2022-09-22 at 09:38 -0700 Jeremy Allison via samba sent off:
> > So samba would need to take into account that not all filesystems
> > support extended attributes as a whole but might support some
> > operations on them but not others.
>
> No, that way lies insanity and unmaintainable complexity in
> Samba. Blame POSIX (again) for not standarizing EA behavior.
sorry, but POSIX is not to blame here. NFS4 ACLs are the only standardized ACL
implementation. The is no such thing as "POSIX ACLs". POSIX ACLs have always
only been a draft. The draft was never finalized. All the UNIX falvours
implemented different draft version, this is also why it does not make any
sense to talk about a POSIX ACL standard here. Some implement for example DENY
ACEs, some don't. Some implement default ACEs, some don't. Some implement a
access mask, some don't. All of them are completely proprietary. In our Samba
documentation we still give the implession that POSIX ACLs are a kind of
standard. Honestly however, this is only the limited Linux proprietary version
that we document and implement.
All UNIX flavors (except for Linux however) support actually *standardized*
NFS4 ACLs. They were standardized by the same people to withdrew the previously
proposed POSIX ACL drafts.
I see more and more customers running into the limitation, that neither the
Linux SMB nor the NFS4 client implmentations satisfy their needs because NFS4
ACLs are non-existing in the Linux world and the management of NFS4 ACLs on
POSIX clients, even if supported server-side, is a pita. Frankly speaking, for
the majority of Samba fileserver setups actually Linux is no longer the
recommended platform. There is *one* good reason, why NAS vendors prefer
FreeBSD these days: the lack of NFS4 ACLs.
Björn
--
SerNet GmbH - Bahnhofsallee 1b - 37081 Göttingen
phone: +495513700000 mailto:contact@sernet.com
AG Göttingen: HR-B 2816 - https://www.sernet.com
Manag. Directors Johannes Loxen and Reinhild Jung
data privacy policy https://www.sernet.de/privacy
parent reply other threads:[~2022-09-26 8:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <YyyPfX7J2LKEI4QG@jeremy-acer>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220923175354.GA574247@sernet.de \
--to=bjacke@sernet.de \
--cc=jra@samba.org \
--cc=kobras@puzzle-itc.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lustre-discuss@lists.lustre.org \
--cc=michael.weiser@atos.net \
--cc=samba@lists.samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).