Bug 1030447

Summary: btrfs blocks filesystem operations
Product: [Fedora] Fedora Reporter: Enrico Scholz <rh-bugzilla>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-10 14:41:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
echo w > /proc/sysrq-trigger none

Description Enrico Scholz 2013-11-14 13:16:11 UTC
Created attachment 823933 [details]
echo w > /proc/sysrq-trigger

Description of problem:

When using btrfs, processes accessing the filesystem are stuck in 'D' state after some time.  Disk itself is idle and 'vmstat' does not report io.  Sending SIGKILL or SIGTERM to these processes often recovers the system.

I am not sure whether this is related, but problem seems to start on high i/o load (building of a complete embedded system which includes unpacking, compiling and removal of files) while a backup of a ro-snapshot of the corresponding subvolume will be created (rdiff-backup to a different btrfs fs).

The btrfs fs is on an lvm volume which is on a software raid-1:

Label: none  uuid: dacc4c62-4b8b-4027-83dc-60c19d5ee928
        Total devices 1 FS bytes used 197.08GB
        devid    1 size 330.00GB used 221.82GB path /dev/dm-46

The fs was enlarged several times (lvresize + btrfs fi resize) and I executed 'btrfs balance' some days ago.   I used it most of the time without 'autodefrag' (problem happened there too) but enabled this option some days ago.

A complete manual defragmentation is not possible because it is very slow and will take 10 years or so (a non-recursive 'btrfs defragment' on the top directory of a subvolume takes 10-15 minutes (disk led is indicating activity, but 'vmstat 1' reports only small xfer rates.


I will access 'echo w > /proc/sysrq-trigger' output.  


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

kernel-3.11.7-200.fc19.x86_64

Comment 1 Justin M. Forbes 2014-01-03 22:05:01 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.12.6-200.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.

Comment 2 Justin M. Forbes 2014-03-10 14:41:03 UTC
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested.