Bug 683745

Summary: btrfs / swap problems
Product: [Fedora] Fedora Reporter: Fabian Deutsch <fabian.deutsch>
Component: kernelAssignee: Josef Bacik <jbacik>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-16 20:41:21 UTC Type: ---
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
dmesg none

Description Fabian Deutsch 2011-03-10 09:26:01 UTC 
Description of problem:
After migrating my /home from ext4 to btrfs and upgrading the kernel frpom 2.6.25(?) to 2.6.38-0.rc7 I notice oops when there is a high io on the btrfs partition.

Version-Release number of selected component (if applicable):
# rpm -q kernel btrfs-progs
kernel-2.6.37-0.rc5.git2.1.fc15.i686
kernel-2.6.38-0.rc6.git0.1.fc16.i686
kernel-2.6.38-0.rc7.git2.3.fc16.i686
btrfs-progs-0.19-13.fc15.i686
[root@proprietary ~]# uname -a
Linux proprietary.local 2.6.38-0.rc7.git2.3.fc16.i686 #1 SMP Sat Mar 5 00:09:37 UTC 2011 i686 i686 i386 GNU/Linux

How reproducible:
Quite often.

Steps to Reproduce:
1. migrate a ext4 partition (atop a lvm logvol) to btrfs using btrs-convert
2. rsync many files from that partition to an external usb drive (backup ..)
3.
  
Actual results:
the attached oopses appear

Expected results:
No oopses.

Additional info:
The btrfs partition is atop of a logvol (side effect of the migration from ext4 to btrfs).
Comment 1 Fabian Deutsch 2011-03-10 09:28:33 UTC 
Assigning the bug to Josef, as he asked for btrfs bugs and this bug appeared after my btrfs migration :)
Comment 2 Fabian Deutsch 2011-03-10 09:28:54 UTC 
Created attachment 483395 [details]
dmesg
Comment 3 Josef Bacik 2011-03-16 20:31:05 UTC 
This is the same sort of corruption that will be caught by the fix in 682893.

*** This bug has been marked as a duplicate of bug 682893 ***
Comment 4 Josef Bacik 2011-03-16 20:31:28 UTC 
Crap sorry wrong bug, changing back to assigned.
Comment 5 Fabian Deutsch 2011-03-16 20:41:21 UTC 
This might not be a bug, but corrupt RAM in the affected system. I'll update this, as soon as I confirmed that teh RAM is okay.