Re: NFSv4 ACLs

[steve <steve@steve-ss.com>]

On 22/04/12 01:57, Andrew Bartlett wrote:
> 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.
>

s3 and nfs work fine (maybe others are doing it too?)

We are testing Samba4 and nfs now and yes same data, same box. As yet, 
we've not been able to break it no matter what we throw at it.

When will the oplocks default change? Will it affect us?

Cheers,
Steve