Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionOrion Poplawski
2012-03-29 15:41:46 UTC
Created attachment 573712[details]
test c program
Description of problem:
client A:
touch blah
ln -s blah blahlink
client B:
open("blahlink", O_RDONLY|O_CREAT, 0666) = -1 EEXIST (File exists)
$ ls -l blahlink
lrwxrwxrwx. 1 orion cora 4 Mar 29 09:30 blahlink -> blah
open("blahlink", O_RDONLY|O_CREAT, 0666) = 3
Removing and recreating the link on client A restores the problem.
earth:/export/home/orion on /home/orion type nfs (rw,noatime,intr,rsize=32768,wsize=32768,actimeo=1,sloppy,vers=4,addr=10.10.10.1,clientaddr=10.10.41.10)
I thought this might be the same as bug 739797, but this kernel should have the fix for that (and in fact it does fix the vim issue).
Version-Release number of selected component (if applicable):
2.6.32-250.el6.x86_64
How reproducible:
Everytime
I can also reproduce with 2.6.42.9-2.fc15.x86_64 but not with 3.3.0-4.fc16.x86_64.
Scratch that. I can reproduce with 3.3.0-4.fc16.x86_64. You need to make sure that the link is recreated after an initial access/mount to test. Also present in 3.4.0-0.rc0.git1.2.fc18.x86_64. I can't reproduce with 2.6.18-308.1.1.el5.
Created attachment 575818[details]
proposed patch
This was the proposed patch on the list. I applied to kernel-2.6.32-220.7.1.el6.x86_64 and it appears to have fixed the issue.
Comment 5RHEL Program Management
2012-05-03 05:24:31 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 7RHEL Program Management
2012-06-27 13:50:30 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-0496.html