Bug 680654 - /home on btrfs is quite unusable.
Summary: /home on btrfs is quite unusable.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Josef Bacik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-26 18:53 UTC by Fabian Deutsch
Modified: 2011-06-08 21:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-08 21:33:45 UTC
Type: ---


Attachments (Terms of Use)

Description Fabian Deutsch 2011-02-26 18:53:48 UTC
Description of problem:
I converted my ext3 based /home to btrfs using btrfs-convert.
After the conversion the system felt sluggish.
Especially empathy was nearly not working at all, because it got stalled.
Also Firefox took several minutes to start. Then it told me about some problems.

I converted the partition using a 2.36 kernel (not instaleld anymore). But mounting the partition with it raised kerneloops. So i used the partition with the 2.6.38 kernel below.

Version-Release number of selected component (if applicable):
$ rpm -q kernel btrfs-progs
kernel-2.6.35.9-64.fc14.i686
kernel-2.6.37-0.rc5.git2.1.fc15.i686
kernel-2.6.38-0.rc6.git0.1.fc16.i686
btrfs-progs-0.19-12.fc14.i686

How reproducible:


Steps to Reproduce:
1. Convert a ~3year old ext3 partition to btrfs: btrfs-convert /dev/mapper/Log...
2. Change fstab (just changed the filesystem to btrfs)
3. Reboot
  
Actual results:
Booting is fine.
Using aplication within my Xsession is a no-go.

Expected results:
Everything is fine.

Additional info:

Comment 1 Fabian Deutsch 2011-03-10 08:34:34 UTC
The problem appeared to be a quite-full /home. I just had 5% of free space.
After freeing some more space (30%) the conversion was successful and it is working fine.

Comment 2 Josef Bacik 2011-06-08 21:33:45 UTC
great let me know if you have any other issues.


Note You need to log in before you can comment on or make changes to this bug.