 | | | getxattr() problem with NFS client? | getxattr() problem with NFS client? 2005-01-10 - By Tom Sightler
Back
On Mon, 2005-01-10 at 13:37 -0800, Garrick Staples wrote:
> So far, I have two workarounds, loading the nfs module with
> nfs3_acl_max_entries=0 or mounting with nfsvers=2. The redhat docs mention a
> mount option of "no_acl" but that option doesn't actually exist.
My guess is your seeing the infamous NFS bug. Do you have to go all the
way to nfs3_acl_max_entries = 0? What about nfs3_acl_max_entries=256
(the default is 1024 which requires an order 2 allocation while setting
of 256 supposedly only requires a order 0 allocation)? That should lower
the threshold enough to workaround the bug while still allowing for
ACL's to work (assuming you need them).
Later,
Tom
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
On Mon, 2005-01-10 at 13:37 -0800, Garrick Staples wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">So far, I have two workarounds, loading the nfs module
with</FONT>
<FONT COLOR="#000000">nfs3_acl_max_entries=0 or mounting with nfsvers=2. The
redhat docs mention a</FONT>
<FONT COLOR="#000000">mount option of "no_acl" but that option doesn
't actually exist.</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
My guess is your seeing the infamous NFS bug. Do you have to go all the
way to nfs3_acl_max_entries = 0? What about nfs3_acl_max_entries=256 (the
default is 1024 which requires an order 2 allocation while setting of 256
supposedly only requires a order 0 allocation)? That should lower the threshold
enough to workaround the bug while still allowing for ACL's to work (assuming
you need them).<BR>
<BR>
Later,<BR>
Tom<BR>
<BR>
</BODY>
</HTML>
--
Taroon-list mailing list
Taroon-list@(protected)
http://www.redhat.com/mailman/listinfo/taroon-list
Earn $52 per hosting referral at Lunarpages.
|
|
|