Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Jorg Bornschein" <jb@capsec.org>
To: "Qu Wenruo" <quwenruo@cn.fujitsu.com>,
	"Goldwyn Rodrigues" <rgoldwyn@suse.de>,
	linux-btrfs@vger.kernel.org
Subject: Re: Very slow balance / btrfs-transaction
Date: Mon, 06 Feb 2017 09:14:40 +0000	[thread overview]
Message-ID: <22abce5d39112d2223580b19b1adc4df@85337f6d4fa4> (raw)
In-Reply-To: <57259b63-2f26-0da4-16f6-5fbd781daeb0@cn.fujitsu.com>

February 6, 2017 1:45 AM, "Qu Wenruo" <quwenruo@cn.fujitsu.com> 

> Would you please provide the kernel version?
> 
> v4.9 introduced a bad fix for qgroup balance, which doesn't completely fix qgroup bytes leaking,
> but also hugely slow down the balance process:
>

I'm a bit behind the times: 4.8.13-1-ARCH



   j

  reply	other threads:[~2017-02-06  9:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 22:13 Very slow balance / btrfs-transaction jb
2017-02-03 23:25 ` Goldwyn Rodrigues
2017-02-04  0:30   ` Jorg Bornschein
2017-02-04  1:07     ` Goldwyn Rodrigues
2017-02-04  1:47       ` Jorg Bornschein
2017-02-04  2:55         ` Lakshmipathi.G
2017-02-04  8:22           ` Duncan
2017-02-06  1:45         ` Qu Wenruo
2017-02-06  9:14           ` Jorg Bornschein [this message]
2017-02-06  9:29             ` Qu Wenruo
2017-02-06 16:09           ` Goldwyn Rodrigues
2017-02-07  0:22             ` Qu Wenruo
2017-02-07 15:55               ` Filipe Manana
2017-02-08  0:39                 ` Qu Wenruo
2017-02-08 13:56                   ` Filipe Manana
2017-02-09  1:13                     ` Qu Wenruo
2017-02-04 20:50       ` Jorg Bornschein
2017-02-04 21:10         ` Kai Krakow
2017-02-06 13:19           ` Austin S. Hemmelgarn
2017-02-07 19:47             ` Kai Krakow
2017-02-07 19:58               ` Austin S. Hemmelgarn
  -- strict thread matches above, loose matches on Subject: below --
2017-07-01 14:24 Sidney San Martín

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=22abce5d39112d2223580b19b1adc4df@85337f6d4fa4 \
    --to=jb@capsec.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.com \
    --cc=rgoldwyn@suse.de \
    /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