Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <3c399c3523674ec7b650b647179d7c96@tu-berlin.de>
In-Reply-To: <3c399c3523674ec7b650b647179d7c96@tu-berlin.de>
From:   Nico Kadel-Garcia <nkadel@gmail.com>
Date:   Thu, 2 Jul 2020 21:20:28 -0400
Message-ID: <CAOCN9rz8m1Z75ObhC21V=jizPnEkfFaZv-1Yz4M5zsT19BR97g@mail.gmail.com>
Subject: Re: [Samba] Multiprotocol File Sharing via NFSv4 and Samba
To:     "Kraus, Sebastian" <sebastian.kraus@tu-berlin.de>
Cc:     "samba@lists.samba.org" <samba@lists.samba.org>,
        "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

On Thu, Jul 2, 2020 at 2:16 PM Kraus, Sebastian via samba
<samba@lists.samba.org> wrote:
>
> Hi all,
> are there any non-commercial solutions (apart from solutions like Dell EM=
C, IBM and NetApp) around that allow to simultaneously access the same file=
 system via NFSv4 and Samba exports in a (nearly) non-conflicting manner, e=
specially w.r.t. to NFSv4/Windows ACL incompatibilities?
>
> Best
> Sebatian

I've done it at a commercial scale with locally configured NFS on
Linux clients and Samba for CIFS access on windows clients. It's very
tricky to scale, and to maintain consistent privileges. NFSv4 map
somewhat, but not *perfectly* to CIFS credentials. And lock files
become an adventure, because clients *cannot* be entirely in sync with
a centralized server, the constant monitoring and updating to be in
tight4er and tighter sync themselves cost bandwidth and CPU. So
collaboration working with the same files can require thoughtful
programming to ensure atomic operation. I don't recommend it: I'd
generally recommend picking one protocol or the other and using it
everywhere. It's extraordinarily difficult to predict
incompatibilities someone may run into with ocmmercial software,
written to use lock files with *very* peculiar behavior. And of course
there is the filesystem namespace collission issue. In NFS, README.md"
is a different file from README.MD or readme.md, and resolving this
with CIFS clients o the same workspace can be an adventure.

There are many inexpensive office grade petabyte storage servers which
rely on Samba internally and would probably serve your needs.