Hide Forgot
Created attachment 418880 [details] fsstress panic log Description of problem: Run fsstress test on btrfs may cause kernel bug and panic. Attachment is console log. Version-Release number of selected component (if applicable): [root@amd-drachma-01 ~]# uname -a Linux amd-drachma-01.lab.bos.redhat.com 2.6.32-27.el6.x86_64 #1 SMP Tue May 18 12:25:26 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux [root@amd-drachma-01 ~]# rpm -q btrfs-progs nfs-utils rpcbind btrfs-progs-0.19-10.el6.x86_64 nfs-utils-1.2.2-2.el6.x86_64 rpcbind-0.2.0-4.1.el6.x86_64 Also on RHEL6.0-Snapshot-5, that is 2.6.32-28.el6.x86_64 How reproducible: About 50% Steps to Reproduce: 1. Schedule /kernel/filesystems/btrfs/fsstress in rhts or beaker 2. Or yum install rh-tests-kernel-filesystems-btrfs-fsstress then cd to /mnt/tests/kernel/filesystems/btrfs/fsstress, make run manually Actual results: kernel bug and panic Expected results: Pass test all the time Additional info: rhts job link http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=160738 beaker job link https://beaker.engineering.redhat.com/jobs/1373 And there is a PASS test in beaker, but fsstress process may be stuck. https://beaker.engineering.redhat.com/jobs/1388 https://beaker.engineering.redhat.com/logs/2010/88/1388/2558/24768/113246///console_dmesg--kernel-filesystems-btrfs-fsstress.log
It looks like there was not actually a bug or a panic, but there was a soft lockup and a WARNING due to list corruption, which is bad enough ...
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.
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. **
Josef, can you validate that this does not happen in the current 6.0 builds and close it if not? If it is still an issue, we should reflag this for 6.1 since we are not going to have tech preview items be blockers unless really severe. Thanks!
I ran xfstests against the updated btrfs in RHEL6 and I didn't get any panics (it runs fsstress), so I'm going to close this.