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.
DescriptionPierguido Lambri
2013-03-12 10:28:49 UTC
Description of problem:
Got a kernel panic when trying to use a btrfs file system created on RHEL6.3.
This does not happen if the file system is created with the 6.4 tools.
Version-Release number of selected component (if applicable):
btrfs-progs-0.20-0.2.git91d9eec.el6.x86_64 Fri Feb 22 14:02:04 2013
kernel-2.6.32-358.el6.x86_64 Fri Feb 22 13:57:36 2013
How reproducible:
Steps to Reproduce:
1. Create a file system on RHEL 6.3
2. Update the system to 6.4
3. Try to mount the file system on 6.4
Actual results:
Kernel panic
Expected results:
It shouldn't panic
Additional info:
Comment 4RHEL Program Management
2013-10-13 23:49:54 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
I wonder if my problem is the same, is similar for sure
I'm having a btrfs volume that if exist in fstab kernel panics at boot time (snap attached) but will mount just fine afterwards when system has booted up
it seems that kernel panics are caused by erroneous btrfs filesystem (btrfsck it), at least in my case,
I wonder if all this was caused by missing !!!! /dev/btrfs-control.
should it not be in initrams (dracut modules)
probably should be a separate bug in RHEL 6.4
This should actually be fixed by:
4e0879b [fs] btrfs: don't oops on mount failure due to unsupported features
which fixed:
889471 - [Btrfs] BUG: unable to handle kernel NULL pointer dereference at (null) btrfs_get_sb should return error when open_ctree f
and it's a kernel bug, so tweaking all those fields...
*** This bug has been marked as a duplicate of bug 889471 ***