* NFSACL broken from 3.13 to 3.14
@ 2014-05-08 22:19 JA Magallón
0 siblings, 0 replies; 3+ messages in thread
From: JA Magallón @ 2014-05-08 22:19 UTC (permalink / raw)
To: Linux Kernel
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
--
J.A. Magallon <jamagallonn()gmail!com> \ Winter is coming...
^ permalink raw reply [flat|nested] 3+ messages in thread
* NFSACL broken from 3.13 to 3.14
@ 2014-05-15 14:25 JA Magallón
2014-05-15 15:33 ` Christoph Hellwig
0 siblings, 1 reply; 3+ messages in thread
From: JA Magallón @ 2014-05-15 14:25 UTC (permalink / raw)
To: Linux Kernel
(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
--
J.A. Magallon <jamagallon()ono!com> \ Winter is coming...
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: NFSACL broken from 3.13 to 3.14
2014-05-15 14:25 JA Magallón
@ 2014-05-15 15:33 ` Christoph Hellwig
0 siblings, 0 replies; 3+ messages in thread
From: Christoph Hellwig @ 2014-05-15 15:33 UTC (permalink / raw)
To: JA Magall??n; +Cc: Linux Kernel, linux-nfs
On Thu, May 15, 2014 at 04:25:47PM +0200, JA Magall??n wrote:
> 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 ?
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-05-15 15:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-05-08 22:19 NFSACL broken from 3.13 to 3.14 JA Magallón
-- strict thread matches above, loose matches on Subject: below --
2014-05-15 14:25 JA Magallón
2014-05-15 15:33 ` Christoph Hellwig
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox