 | | | getxattr() problem with NFS client? | getxattr() problem with NFS client? 2005-01-10 - By Garrick Staples
Back
We just moved a ton of filesystems over to Solaris samfs/qfs volumes and they
are NFS exported to a bunch of rhel3 clients. Sometimes after modifying a
file, I'm seeing problems trying to access the files for about 15 seconds.
Just doing an 'ls -l' prints an IO error...
$ strace ls -l foo
...
lstat64("foo", {st_mode=S_IFREG|0644, st_size=4900, ...}) = 0
getxattr("foo", "system.posix_acl_access", (nil), 0) = -1 EIO (Input/output
error)
After about 15 seconds, getxattr() will return ENODATA.
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.
Any thoughts from the Taroon crowd? Is this an NFS client bug? Solaris NFS
clients aren't having any problems.
--
Garrick Staples, Linux/HPCC Administrator
University of Southern California
--
Taroon-list mailing list
Taroon-list@(protected)
http://www.redhat.com/mailman/listinfo/taroon-list
Earn $52 per hosting referral at Lunarpages.
|
|
|