Red Hat Bugzilla – Bug 445957
Change "decode_getfattr: xdr error %d!" to dprintk
Last modified: 2011-02-16 10:33:56 EST
Description of problem:
On RHEL-4, latest kernel and nfs-utils package, the logs are filled with the
error message below while stating a file which has nfsv4 acls set on it and is
mounted on RHEL-4 client via sec=krb5i.
decode_getfattr: xdr error 13!
We can see that in the RHEL-4 sources (fs/nfs/nfs4xdr.c::decode_getfattr) that
message comes from an explicit printk, while on RHEL-5 and upstream it is a
dprintk. It would be interesting to turn that to a dprintk in RHEL-4 as well
so that we don't scare people and fill up logs unnecessarily.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Setup a Solaris 10 box as NFS server and a RHEL-4 box as nfs client. Create an
export on the server containing files with ACLs.
Log on to the RHEL4 client system, run "service rpcgssd restart" and mount the
share from the server:
# mount -t nfs4 solaris:/export /nfs4 -o sec=krb5i
Run "ls -l /nfs4"
Check /var/log/messages and see the errors.
Error messages flood the logs and console.
Error messages should be printed only when debug is turned on.
Updating PM score.
Since RHEL 4.8 External Beta has begun, and this bugzilla remains
unresolved, it has been rejected as it is not proposed as exception or
*** Bug 496960 has been marked as a duplicate of this bug. ***
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Committed in 89.11.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.