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.

+++ This bug was initially created as a clone of Bug #652321 +++

Created attachment 459791 [details]
fix patch

Description of problem:

jbd2_stats_proc_init() was located on a wrong place. The /proc/fs/jbd2/<dev>/ cannot be create when use a external journal device. Note that this problem exist in rhel6 also.

Version-Release number of selected component (if applicable):
2.6.18-* 2.6.32-*

--- Additional comment from esandeen on 2010-11-11 11:48:45 EST ---

It'd be great if you could send this patch upstream as well, thanks.  That way it'll be fixed upstream and you'll get credit for the fix.

After that it looks quite reasonable for a RHEL6 fix.

Thanks,
-Eric

--- Additional comment from rwheeler on 2010-11-11 12:35:23 EST ---

It would also be great to have you report this issue through your official support channel if you have a RHEL subscription or via your partner engineering contact. That way, we can track it properly as we put together issues that make a release.

Thanks!

This was fixed with upstream commit 0587aa3d11f9769a301b21bff2c3ed8365606b8d.

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.

Patch(es) available on kernel-2.6.32-112.el6

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-2011-0542.html