From: "JA Magallón" <jamagallonn@gmail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: NFSACL broken from 3.13 to 3.14
Date: Fri, 09 May 2014 00:19:50 +0200 [thread overview]
Message-ID: <536C0306.50202@gmail.com> (raw)
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...
next reply other threads:[~2014-05-08 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 22:19 JA Magallón [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-15 14:25 NFSACL broken from 3.13 to 3.14 JA Magallón
2014-05-15 15:33 ` Christoph Hellwig
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=536C0306.50202@gmail.com \
--to=jamagallonn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox