public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Torcz <tomek@pipebreaker.pl>
To: linux-btrfs@vger.kernel.org
Subject: Re: yum upgrade on btrfs very slow
Date: Tue, 29 Sep 2009 08:18:22 +0200	[thread overview]
Message-ID: <20090929061822.GB15930@mother.pipebreaker.pl> (raw)
In-Reply-To: <20090928133543.GB6405@think>

On Mon, Sep 28, 2009 at 09:35:43AM -0400, Chris Mason wrote:
> On Mon, Sep 28, 2009 at 02:18:27PM +0200, Tomasz Torcz wrote:
> > 
> >   Hi,
> > 
> >  I'm using btrfs as rootfs on my Fedora 12 (rawhide) test system.
> > Every yum activity is very slow, like 15 minutes for installation of 11
> > packages 25MB in size. Kernel is 2.6.31.1-48.fc12.x86_64, btrfs-progs-0.19-7.fc12.x86_64.
> > Hardware is pentium 4 3.0 GHz (Hyperthreading, 64 bit), with single IDE disk 
> > on Intel ICH controller.
> 
> You're doing quite a lot of reads, and some writes.  Could you please
> capture the output of sysrq-w at 5s intervals during the upgrade?

  It got quite big (over 100 KiB, over 1 MiB after unpacking), so I
put it at http://pipebreaker.pl/dump/sysrq-w_every_5_sec.txt.bz2

-- 
Tomasz Torcz                Only gods can safely risk perfection,
xmpp: zdzichubg@chrome.pl     it's a dangerous thing for a man.  -- Alia


  reply	other threads:[~2009-09-29  6:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 12:18 yum upgrade on btrfs very slow Tomasz Torcz
2009-09-28 13:35 ` Chris Mason
2009-09-29  6:18   ` Tomasz Torcz [this message]
2009-09-29 13:25     ` Chris Mason
2009-09-30 19:43       ` Tomasz Torcz
2009-10-01  9:01         ` Tomasz Torcz
2009-10-21  9:27           ` Tomasz Torcz
2009-10-26  8:55             ` Chris Mason
2009-10-26 13:35               ` Tomasz Torcz
2009-10-01  9:04         ` Jens Axboe
2009-10-05 12:09           ` Ric Wheeler

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=20090929061822.GB15930@mother.pipebreaker.pl \
    --to=tomek@pipebreaker.pl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox