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.
DescriptionLans Carstensen
2011-09-16 18:11:52 UTC
Created attachment 523599[details]
/var/log/messages and "thread apply all bt full" from cfuse process
Description of problem:
During Ceph 0.34 FUSE client testing we caused oddities in current/released RHEL 6.1 kernels. I'm attaching a simple repro, sysrq+w output from two hangs and one after I killed off the cfuse process the second time, and a "thread apply all bt full" from the cfuse userspace process. I can often, but not always, recover by kill -9'ing cfuse and umount'ing the cfuse mountpoint.
Version-Release number of selected component (if applicable):
kernel-2.6.32-131.12.1.el6.x86_64
ceph & ceph-fuse 0.34
How reproducible:
100% in my environment
Steps to Reproduce:
1. Set up a Ceph server, set up a client keyring for client.yourhostname
2. cfuse /mnt --name=client.yourhostname
while(1)
dd if=/dev/zero of=/mnt/file bs=1M count=1
/bin/rm /mnt/file
end
Actual results:
Files created/removed, then mountpoint hangs and causes other odd kernel lockups.
Expected results:
Files created/removed
Additional info:
Since RHEL 6.2 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.
I got assigned to this bug, but it's a very old bug.
Lans, can you let me know if you can still reproduce it on newer versions of RHEL6? If so, can you provide kernel stack traces of the hung processes? in the messages file attached, no stack traces from kernel side are available.
Thanks.
Created attachment 523599 [details] /var/log/messages and "thread apply all bt full" from cfuse process Description of problem: During Ceph 0.34 FUSE client testing we caused oddities in current/released RHEL 6.1 kernels. I'm attaching a simple repro, sysrq+w output from two hangs and one after I killed off the cfuse process the second time, and a "thread apply all bt full" from the cfuse userspace process. I can often, but not always, recover by kill -9'ing cfuse and umount'ing the cfuse mountpoint. Version-Release number of selected component (if applicable): kernel-2.6.32-131.12.1.el6.x86_64 ceph & ceph-fuse 0.34 How reproducible: 100% in my environment Steps to Reproduce: 1. Set up a Ceph server, set up a client keyring for client.yourhostname 2. cfuse /mnt --name=client.yourhostname while(1) dd if=/dev/zero of=/mnt/file bs=1M count=1 /bin/rm /mnt/file end Actual results: Files created/removed, then mountpoint hangs and causes other odd kernel lockups. Expected results: Files created/removed Additional info: