From: Brian De Wolf <bldewolf@csupomona.edu>
To: linux-nfs@vger.kernel.org
Subject: nfs4_getfacl "Failed getxattr operation" when too many ACL entries exist
Date: Thu, 10 Apr 2008 14:53:44 -0700 [thread overview]
Message-ID: <47FE8C68.50502@csupomona.edu> (raw)
Recently we've been prototyping serving Solaris ZFS exports via NFSv4 to some
Linux hosts. These will some day be exposed to general users, so I've been
testing things to see if I can break them. Anyway, it seems that nfs4_getfacl
is only able to read ACLs with up to 208 entries. nfs4_setfacl is able to
insert a 209th entry, but any attempts to view or edit the ACLs after that fail
with:
Failed getxattr operation
: Input/output error
There are two ways to make the ACLs readable again:
1) Have someone log in to the Solaris box and remove some of the entries
2) Reset the ACLs using nfs4_setfacl -s `some spec`
Has anyone run into this issue before? Is it fixable? I didn't reach the same
problem locally on the Solaris box, nor on another Solaris box with the same NFS
mount, so it looks like it's a problem specific to Linux. Here's the versions
of relevant packages on the test box running Gentoo (did I miss any?):
Kernel: 2.6.23-gentoo-r8
nfs-utils-1.1.0-r1
attr-2.4.39
nfs4-acl-tools-0.3.2
next reply other threads:[~2008-04-10 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 21:53 Brian De Wolf [this message]
2008-04-10 22:35 ` nfs4_getfacl "Failed getxattr operation" when too many ACL entries exist david m. richter
2008-04-10 22:41 ` david m. richter
2008-04-11 19:33 ` J. Bruce Fields
2008-04-11 21:43 ` nfs4_getfacl "Failed getxattr operation" when too many ACLentries exist Brian De Wolf
2008-04-11 22:26 ` david m. richter
2008-04-11 23:31 ` Brian De Wolf
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=47FE8C68.50502@csupomona.edu \
--to=bldewolf@csupomona.edu \
--cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.