From: mck <mck@apache.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs slowdown
Date: Wed, 03 Aug 2011 17:56:33 +0200 [thread overview]
Message-ID: <1312386993.23947.7.camel@localhost> (raw)
In-Reply-To: <4E2D3B4D.8050301@podzimek.org>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
I can confirm this as well (64-bit, Core i7, single-disk).
> The issue seems to be gone in 3.0.0.
After a few hours working 3.0.0 slows down on me too. The performance
becomes unusable and a reboot is a must. Certain applications
(particularly evolution ad firefox) are next to permanently greyed out.
I have had a couple of corrupted tree logs recently and had to use
btrfs-zero-log (mentioned in an earlier thread). Otherwise returning to
2.6.38 is the workaround.
~mck
--
"A mind that has been stretched will never return to it's original
dimension." Albert Einstein
| www.semb.wever.org | www.sesat.no
| http://tech.finn.no | http://xss-http-filter.sf.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-08-03 15:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 7:54 Btrfs slowdown Christian Brunner
2011-07-25 8:51 ` Andrej Podzimek
2011-07-25 9:45 ` Andrej Podzimek
2011-08-03 15:56 ` mck [this message]
2011-07-25 14:37 ` Jeremy Sanders
2011-07-25 19:52 ` Chris Mason
2011-07-27 8:41 ` Christian Brunner
2011-07-28 4:05 ` Marcus Sorensen
2011-07-28 15:10 ` Christian Brunner
2011-07-28 15:10 ` Christian Brunner
2011-07-28 16:01 ` Sage Weil
2011-08-08 21:58 ` Sage Weil
2011-08-09 13:33 ` Christian Brunner
2011-08-09 13:33 ` Christian Brunner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1312386993.23947.7.camel@localhost \
--to=mck@apache.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.