This is a RHEL 5 report for bz 225507. The report is based on the upstream thread http://linux-nfs.org/pipermail/nfsv4/2007-December/007321.html To recreate: 1) On the server, set anonuid/anongid as 4294967294 # cat /etc/exports /export *(rw,insecure,fsid=0) /export/data *(rw,anonuid=4294967294,anongid=4294967294) Restart nfs to export the filesystem 2) On the server create a file with uid set to 4294967294 mkdir /export/data/test touch /export/data/test/a chown 4294967294 /export/data/test/a 3) Mount the nfs4 export on a client mount -r nfs4 server:/data /mnt 4) cd /mnt/test/ 5) ls -l The system will hang. The upcall by the nfs module uses a signed number. Thus the uid 4294967294 gets translated to -2 which confuses rpc.idmapd.
Patch available at http://linux-nfs.org/pipermail/nfsv4/2007-December/007321.html
A test kernel with the patch from c#1 was tested successfully by the user.
Patch looks straightforward and obviously correct. I've added it to my test kernels here to get some soak time: http://people.redhat.com/jlayton/ ...I'd also think I see the problem with idmapd that causes it to stop responding. For most error conditions, the nfsdcb() function does not requeue the event (i.e. call event_add() again). That means that once we hit an error condition idmapd stops watching that file descriptor. I've got a patch that should help fix that, but it needs to be tested a little more and I want to get some upstream feedback on it.
Patch for idmapd sent upstream. If it gets accepted I'll plan to clone this bug and we'll get this patch into RHEL too: http://marc.info/?l=linux-nfs&m=125261173214324&w=2
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 release.
in kernel-2.6.18-168.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 Please do NOT transition this bugzilla state to VERIFIED until our QE team has sent specific instructions indicating when to do so. However feel free to provide a comment indicating that this fix has been verified.
~~ Attention Customers and Partners - RHEL 5.5 Beta is now available on RHN ~~ RHEL 5.5 Beta has been released! There should be a fix present in this release that addresses your request. Please test and report back results here, by March 3rd 2010 (2010-03-03) or sooner. Upon successful verification of this request, post your results and update the Verified field in Bugzilla with the appropriate value. If you encounter any issues while testing, please describe them and set this bug into NEED_INFO. If you encounter new defects or have additional patch(es) to request for inclusion, please clone this bug per each request and escalate through your support representative.
who is Pierre? seems he isn't in CC list. if he could provides test result?
can reproduce on 5.4: 1) On the server, set anonuid/anongid as 4294967294 # cat /etc/exports /export *(rw,insecure,fsid=0) /export/data *(rw,anonuid=4294967294,anongid=4294967294) Restart nfs to export the filesystem 2) On the server create a file with uid set to 4294967294 mkdir /export/data/test touch /export/data/test/a chown 4294967294 /export/data/test/a 3) Mount the nfs4 export on a client mount -t nfs4 server:/data /mnt or: mount -t nfs4 localhost:/data /mnt 4) cd /mnt/test/ 5) ls -l check error: # vim /var/log/messages Mar 2 02:53:40 amd-chipotle-01 rpc.idmapd[7117]: nfsdcb: id '-2' too big! verify on 5.5 kernel 2.6.18-190.el5 and no problem.
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. http://rhn.redhat.com/errata/RHSA-2010-0178.html
*** Bug 533835 has been marked as a duplicate of this bug. ***