All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Balance performance problem with 3.14.1
Date: Thu, 8 May 2014 15:07:40 +0000 (UTC)	[thread overview]
Message-ID: <pan$bfb68$5387197d$eb4cee58$e8e950f0@cox.net> (raw)
In-Reply-To: 201405081950.23922.russell@coker.com.au

Russell Coker posted on Thu, 08 May 2014 19:50:23 +1000 as excerpted:

> I've got a server/workstation (KDE desktop and file server) running
> kernel 3.14.1 from the Debian package 3.14-trunk-amd64.
> 
> It was running well until I decided to do a full balance of the BTRFS
> RAID-1 array of 3TB SATA disks (which hadn't been balanced before due to
> previous kernels performing badly with scrub or balance).  I canceled
> the balance after about 5 days when it had been claiming to be about 65%
> done for a day while doing a lot of disk IO.
> 
> After canceling the balance the performance of the array has been poor.

Not much help, but two comments:

1) I've seen other reports of performance problems after balance.  Nobody 
seems to have a good reason as to why a balance might do that.

2) I've NOT seen anything like that, here.  However, my btrfs are all 
rather small, under 50 GiB.

(FWIW, it /still/ seems weird to me calling a GB "small".  It doesn't 
seem all /that/ long ago that I bought my first 1 GB drive, and it sure 
wasn't small nor inexpensive then!  I guess I've officially joined the 
computer old-timers!)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-05-08 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08  9:50 Balance performance problem with 3.14.1 Russell Coker
2014-05-08 15:07 ` Duncan [this message]
2014-05-08 16:10 ` Josef Bacik
2014-05-12  2:17   ` Russell Coker
  -- strict thread matches above, loose matches on Subject: below --
2014-05-08 11:47 Tomasz Chmielewski

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='pan$bfb68$5387197d$eb4cee58$e8e950f0@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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.