From: Andrew Bartlett <abartlet@samba.org>
To: steve <steve@steve-ss.com>
Cc: simo <idra@samba.org>,
linux-nfs@vger.kernel.org,
"samba-technical@lists.samba.org"
<samba-technical@lists.samba.org>, Jeremy Allison <jra@samba.org>,
Ondrej Valousek <webserv@s3group.com>
Subject: Re: NFSv4 ACLs
Date: Sun, 22 Apr 2012 09:57:38 +1000 [thread overview]
Message-ID: <1335052658.17583.4.camel@obed> (raw)
In-Reply-To: <4F929B50.1020407@steve-ss.com>
On Sat, 2012-04-21 at 13:34 +0200, steve wrote:
> On 21/04/12 03:34, simo wrote:
> > On Fri, 2012-04-20 at 18:08 -0400, J. Bruce Fields wrote:
> >> On Fri, Apr 20, 2012 at 02:59:45PM -0700, Jeremy Allison wrote:
> >>> On Fri, Apr 20, 2012 at 05:26:27PM -0400, J. Bruce Fields wrote:
> >>>> On Fri, Apr 20, 2012 at 11:55:53AM -0700, Jeremy Allison wrote:
> >>>>> On Fri, Apr 20, 2012 at 12:04:02PM +0200, Ondrej Valousek wrote:
> >>>>>> Hi List,
> >>>>>>
>
> >
> >> (By the way, is reexporting nfs with samba really going to work well
> >> anyway?)
> >
> > Not really, it is generally unsupported, except for read only shares. It
> > will work in most of the simple cases for writing .. until it breaks :)
> >
>
> Hi
> That's worrying.
>
> We been rw'ing nfs/samba for years. Maybe we're the only ones. nfs3 for
> our Linux clients and samba for the rest. Same shared data. Only Posix
> acl's though. Maybe that's the simple bit?
> Cheers,
> Steve
Are Samba and NFSd running on the same server, exporting the same data?
That is what is expected to work. See 'kernel oplocks' (the default of
which will change for 4.0) to allow NFS and Samba to break each other's
oplocks.
What Simo cautions about is where an NFS server (say a NAS server)
exports to some direct NFS clients, and then a 'proxy' Samba server is
an NFS client and a Samba server for Windows clients. This 'proxy'
setup is considered dangerous.
Andrew Bartlett
--
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
next prev parent reply other threads:[~2012-04-22 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F913492.8000402@s3group.cz>
[not found] ` <20120420185553.GB32622@samba2>
2012-04-20 21:26 ` NFSv4 ACLs J. Bruce Fields
2012-04-20 21:59 ` Jeremy Allison
2012-04-20 22:08 ` J. Bruce Fields
2012-04-21 1:34 ` simo
2012-04-21 11:34 ` steve
2012-04-21 23:57 ` Andrew Bartlett [this message]
2012-04-23 14:49 ` steve
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=1335052658.17583.4.camel@obed \
--to=abartlet@samba.org \
--cc=idra@samba.org \
--cc=jra@samba.org \
--cc=linux-nfs@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=steve@steve-ss.com \
--cc=webserv@s3group.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.