NFSACL broken from 3.13 to 3.14
Subsystems (2)
(sorry if this gets twice to the list, my ISP's SMPT seems to have gone haywire....)
Hi...
I mount homes from a Solaris 10 server, via NFSv3. Solaris nfs has a special sideband server on a port for NFS to check ACLs. With previous version of kernel (3.13.10 was the latest I check), I need no special option to mount Solaris shares. With 3.14, it began to give errors, directories created with mkdir returned error, files got created but truncated to 0 size... (now I have 3.14.3).
I solved it adding the 'noacl' option to Solaris mount entries in autofs, so the linux clients don't use the sideband protocol.
As I have read, NFSACL usage is negotitated between client and server. Something has changed and the negotiation fails, perhaps ?
Any idea ?
TIA
Signature · 1 line
J.A. Magallon <jamagallon()ono!com> \ Winter is coming...
Quoted 7 lines · JA Magall??n
I mount homes from a Solaris 10 server, via NFSv3. Solaris nfs has a special sideband server on a port for NFS to check ACLs. With previous version of kernel (3.13.10 was the latest I check), I need no special option to mount Solaris shares. With 3.14, it began to give errors, directories created with mkdir returned error, files got created but truncated to 0 size... (now I have 3.14.3).
Quoted 5 lines
I solved it adding the 'noacl' option to Solaris mount entries in autofs, so the linux clients don't use the sideband protocol.
As I have read, NFSACL usage is negotitated between client and server. Something has changed and the negotiation fails, perhaps ?
We have some pretty bug ACL changes in 3.14. I've tested it against a Linux server, but don't have a Solaris server available. Do you have something like strace or wireshark traces to show differences between the versions?