samba - Sep 2016 - still nfs mountpoints do no work as samba shares?

On 01/09/16 15:57, Gaiseric Vandal via samba wrote:
> In the past I used samba shares on top of autofs NFS 
> shares.         I did not try samba over static NFS mounts 
> (file systems mounted by root manually or defined in 
> /etc/fstab.) I suspect therefore that you might have a 
> permissions issue.
I said: ...seems ok on the clients but only - until a user 
want to change content of a file or copy that file..
But I should have been more specific: users can create new 
content(dirs, files) and remove stuff.
Problem almost certainly is not "permissions". It seems 
something with locking mechanism nfs <=> samba.
On Samba box when a user accesses the content directly in 
nfs4 mountpoint this problems do not occur.
>
> I had several servers running NFS and Samba, so this meant 
> that user id's were consistent across all machines for 
> both nfs/unix and samba.     The Projects samba share on 
> the main server was mounted on a /projects autofs top 
> level directory which included sub directories from both 
> the main server and other servers.
>
>
> The better solution (in my opinion) is to install samba on 
> your NFS server as  domain member.  On your primary server 
> you can create MS DFS short cuts to the other server -  so 
> users still can go to the primary server to find files.  
> They will be transparently redirected to the other server.
>
NFS box and Samba box are in separate domains and I don't 
know just yet how to make them trust each other. NFS is IPA 
and Samba is just own BDC.
What even more peculiar - linux smb client also does not 
suffer from this problem. I can in Gnome edit files and do 
things that Win 7 refuses to do.

>
>
>
> On 09/01/16 10:11, lejeczek via samba wrote:
>> hi all
>> I remember that in the past many would say these two do 
>> not go well together, but I wonder if situation improved 
>> now?
>> Reason I'm asking is because I decided to give it another 
>> try and I have an nfs4 mount point that I make a share in 
>> Samba 3.6.23-36.el6_8 and everything seems ok on the 
>> clients but only - until a user want to change content of 
>> a file or copy that file, then infamous:
>> "..cannot access the file because another process..."
>>
>> I'm trying usual:
>>
>> kernel oplocks = no
>> oplocks = no
>>
>> but these do not do anything.
>> Clients are Win 7 and nfs servers runs off Centos 7.2.
>>
>> I wonder if someone, perhaps an expert could say whether 
>> situation has improved and there is a way to samba share 
>> a nfs4 mountpoint?
>>
>> many thanks,
>> L
>>
>
>

Am 02.09.2016 um 10:46 schrieb lejeczek via samba:
> NFS box and Samba box are in separate domains and I don't know just yet
> how to make them trust each other. NFS is IPA and Samba is just own BDC.
> What even more peculiar - linux smb client also does not suffer from
> this problem. I can in Gnome edit files and do things that Win 7 refuses
> to do
most likely because the way the client works is different

many software when you press save is not acting directly with the file 
but creates a new tempfile on the server and finally renames it to the 
old name (with all the problems of that behavior like 
owner/group-changes and refused permissions if you don't have write 
permissions on the folder but on the document itself)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20160902/8ec0a128/signature.sig>

Presuming the NFS server is linux (not solaris )?        I found with 
Office 2007 (vs Office 2003) problems when "saving" created a new 
file.    Most saves with Word and Excel modified the existing file, but 
the 6th or 7th would create a new file then delete the old one.   With 
ZFS as the underlying unix file system getting file permissions correct 
was trickier since ZFS supports more complex ACL's than just classic 
"ugo+rwx."   Powerpoint may actually create a new file every save.

Notepad would not have this issue-  it just modified the file with each 
save.

Linux supports full ACL's but if you are using NFS then you have Windows 
ACL's being imperfectly mapped to  NFS acl's which in turn may be 
imperfectly mapped to Linux ACL's .




If samba is the BDC , what is the PDC?


Generally Samba trusts assume a trust with another Samba or Windows 
domain.  I am not sure how you could "trust" IPA.  Or do you have
Samba
running on the NFS server already ?     In an ideal world you would have 
a common LDAP backend for all accounts that support both unix and samba 
authentication.


On 09/02/16 04:58, Reindl Harald via samba wrote:
>
>
> Am 02.09.2016 um 10:46 schrieb lejeczek via samba:
>> NFS box and Samba box are in separate domains and I don't know just
yet
>> how to make them trust each other. NFS is IPA and Samba is just own
BDC.
>> What even more peculiar - linux smb client also does not suffer from
>> this problem. I can in Gnome edit files and do things that Win 7
refuses
>> to do
>
> most likely because the way the client works is different
>
> many software when you press save is not acting directly with the file 
> but creates a new tempfile on the server and finally renames it to the 
> old name (with all the problems of that behavior like 
> owner/group-changes and refused permissions if you don't have write 
> permissions on the folder but on the document itself)
>
>
>