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.
Created attachment 421174[details]
panic log on kernel 2.6.32-27.el6
Description of problem:
After doing online add/remove device test on btrfs, umount btrfs partition takes long time to finish (about 3 minute), and even may cause kernel panic.
There is no useful log when umount btrfs.
I have only panic log on kernel 2.6.32-27
Version-Release number of selected component (if applicable):
Kernel 2.6.32-33.el6.x86_64
btrfs-progs-0.19-10.el6.x86_64
How reproducible:
umount takes long time: 100%
kernel panic: less than 10%
Steps to Reproduce:
mkdir -p /mnt/btrfs
dd if=/dev/null of=/home/img0 bs=1G seek=5
dd if=/dev/null of=/home/img1 bs=1G seek=3
dd if=/dev/null of=/home/img2 bs=1G seek=2
dd if=/dev/null of=/home/img3 bs=1G seek=1
for i in 0 1 2 3;do losetup /dev/loop$i /home/img$i;done
# Create a filesystem across three drives
mkfs.btrfs /dev/loop0 /dev/loop1 /dev/loop2
mkfs.btrfs /dev/loop3
btrfs-show
mount /dev/loop0 /mnt/btrfs
cp -a /etc /mnt/btrfs
cat /mnt/btrfs/etc/fstab
# Add a device
btrfs-vol -a /dev/loop3 /mnt/btrfs
btrfs-show
cat /mnt/btrfs/etc/fstab
# Remove a device
btrfs-vol -r /dev/loop1 /mnt/btrfs
btrfsck /dev/loop0
btrfs-show
cat /mnt/btrfs/etc/fstab
# Clean up
umount /mnt/btrfs
Actual results:
umount takes about 3min to finish
Expected results:
umount returns within a reasonable time
Additional info:
Comment 2RHEL Program Management
2010-06-07 16:20:46 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Comment 5RHEL Program Management
2010-07-15 15:08:53 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Created attachment 421174 [details] panic log on kernel 2.6.32-27.el6 Description of problem: After doing online add/remove device test on btrfs, umount btrfs partition takes long time to finish (about 3 minute), and even may cause kernel panic. There is no useful log when umount btrfs. I have only panic log on kernel 2.6.32-27 Version-Release number of selected component (if applicable): Kernel 2.6.32-33.el6.x86_64 btrfs-progs-0.19-10.el6.x86_64 How reproducible: umount takes long time: 100% kernel panic: less than 10% Steps to Reproduce: mkdir -p /mnt/btrfs dd if=/dev/null of=/home/img0 bs=1G seek=5 dd if=/dev/null of=/home/img1 bs=1G seek=3 dd if=/dev/null of=/home/img2 bs=1G seek=2 dd if=/dev/null of=/home/img3 bs=1G seek=1 for i in 0 1 2 3;do losetup /dev/loop$i /home/img$i;done # Create a filesystem across three drives mkfs.btrfs /dev/loop0 /dev/loop1 /dev/loop2 mkfs.btrfs /dev/loop3 btrfs-show mount /dev/loop0 /mnt/btrfs cp -a /etc /mnt/btrfs cat /mnt/btrfs/etc/fstab # Add a device btrfs-vol -a /dev/loop3 /mnt/btrfs btrfs-show cat /mnt/btrfs/etc/fstab # Remove a device btrfs-vol -r /dev/loop1 /mnt/btrfs btrfsck /dev/loop0 btrfs-show cat /mnt/btrfs/etc/fstab # Clean up umount /mnt/btrfs Actual results: umount takes about 3min to finish Expected results: umount returns within a reasonable time Additional info: