Bug 625371
Summary: | btrfs: fsstress would be stuck on hp-dl120g6-01.rhts.eng.bos.redhat.com | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Eryu Guan <eguan> | ||||
Component: | kernel | Assignee: | Josef Bacik <jbacik> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 6.1 | ||||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-02-01 18:42:55 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Eryu Guan
2010-08-19 08:14:26 UTC
Josef can you take a look? The backtraces aren't very informative, can I get a sysrq+w? And are we sure we're actually hung and not just taking forever to finish? There have been cases where sync writeback was pretty crappy and taking forever, but eventually finished. Thanks, Josef The fsstress itself was finished eventually and passed, just with these annoying messages showed up. I'll get sysrq+w as soon as I get the host. Created attachment 446162 [details]
fsstress stuck backtrace and sysrq-w state
I attached the full sysrq-w log when got stuck. Hope this can help.
How are you running fsstress btw? And how exactly is this setup, are you exporting the NFS volume from a different machine or the same machine? Have you tried to reproduce this on NFS with an ext4 backend to see if it's just NFS related? I'm trying the fsstress test from xfs and I'll see how that works, but it would be good to be running the same fsstress command as you. That's reasonable. I'll try more cases(ext4 backend, ext4 without nfs). It's a locally exported loop device. Sorry for the late reply. I tried different configurations, and the results are: (NFS exports with rw,fsid=0,insecure,no_subtree_check,sync,no_root_squash) Use NFS NFS mount option [Backend] FS Stuck yes -o hard,intr [0] btrfs Yes yes ---- btrfs No [1] yes -o hard,intr ext4 ?? [2] yes ---- ext4 No no ---- btrfs No no ---- ext4 No [0] The hard option is default on for NFS [1] No stuck found, but got "NFS: file server not responding: still trying. " from console [2] I'll try this once I get the host again. (In reply to comment #8) > I tried different configurations, and the results are: > (NFS exports with rw,fsid=0,insecure,no_subtree_check,sync,no_root_squash) > > Use NFS NFS mount option [Backend] FS Stuck > yes -o hard,intr [0] btrfs Yes > yes ---- btrfs No [1] > yes -o hard,intr ext4 ?? [2] Confirmed mount nfs with -o hard,intr and ext4 as backend fs can pass the test. Run fsstress with -d testdir -p 200 -n 100 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 unfortunately unable to address this request at this time. 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. If you would like it considered as an exception in the current release, please ask your support representative. This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release. 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 unfortunately unable to address this request at this time. 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. If you would like it considered as an exception in the current release, please ask your support representative. This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release. Should be fixed in the backport of btrfs. *** This bug has been marked as a duplicate of bug 663749 *** |