Bug 40842 - Btrfs performance degrades over time
Summary: Btrfs performance degrades over time
Status: RESOLVED OBSOLETE
Alias: None
Product: File System
Classification: Unclassified
Component: btrfs (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: fs_btrfs@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-10 12:56 UTC by Lukáš Karas
Modified: 2013-04-30 16:50 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.0.0
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Munin graph of cpu load (2) (62.89 KB, image/png)
2011-08-10 12:57 UTC, Lukáš Karas
Details
Munin graph of cpu load (1) (31.61 KB, image/png)
2011-08-10 12:58 UTC, Lukáš Karas
Details

Description Lukáš Karas 2011-08-10 12:56:59 UTC
I've dualcore x86_64 server with newest Ubuntu kernel 3.0.0-7-server. On this server is data storage builded from four (1.5T) discs in two raid1 arrays and joined with LVM to 3TB volume. This volume is formated with Btrfs a mounted with default options (rw,noatime). 

On server running corporate NFS and Samba server with same load every day. Everything works fine after reboot, but several days after server load (iowait cpu time) goes to high values and server performance is terrible. IOwait stays high at night too, when nobody works with this server. This situation is visible on munin graphs in attachments.

After unmount and mount this storage again manually everything goes to normal for some next days.

What I can try?
Comment 1 Lukáš Karas 2011-08-10 12:57:46 UTC
Created attachment 68332 [details]
Munin graph of cpu load (2)
Comment 2 Lukáš Karas 2011-08-10 12:58:11 UTC
Created attachment 68342 [details]
Munin graph of cpu load (1)
Comment 3 Lukáš Karas 2011-08-10 16:15:46 UTC
Similar simptoms are described at blog:

http://blog.brendon.com/unix/are-we-in-with-the-new-btrfs-with-nfs-and-esxi/
Comment 4 Josef Bacik 2013-04-30 16:50:02 UTC
Closing, if this is still affecting you on a newer kernel please reopen.

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