linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Leszek Dubiel <leszek@dubiel.pl>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-transacti -- change from be/4 to idle (?)
Date: Wed, 26 Aug 2020 17:39:42 +0800	[thread overview]
Message-ID: <c4359a4d-ae86-1b12-1a33-9372fd81e84e@gmx.com> (raw)
In-Reply-To: <806a0681-6a1b-30d0-de28-8f18019913ad@dubiel.pl>


[-- Attachment #1.1: Type: text/plain, Size: 2591 bytes --]



On 2020/8/26 下午4:58, Leszek Dubiel wrote:
> 
> 
> Hello!
> 
> Process btrfs-transacti takes 100% CPU time and server get very slow.

What's the workload and kernel version?

Workload can tell us if it's really a bug, and different kernel has
quite different perf characteristic, especially if you're using qgroup.
(If you're using qgroup, recent v5.x kernel should have it fixed already)

Thanks,
Qu
> 
> It runs with priority "best effort be/4".
> 
> Is it a good idea to change priority to "idle"?
> 
> 
> 
> 
> 
> root@wawel:/var/log# df -h  /
> 
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/sda2        20T   11T  7.7T  58% /
> 
> 
> 
> root@wawel:/var/log# btrfs sub list / | wc -l
> 
> 367
> 
> 
> 
> root@wawel:/var/log# btrfs dev usag /
> 
> /dev/sda2, ID: 2
>    Device size:             5.45TiB
>    Device slack:              0.00B
>    Data,RAID1:              3.97TiB
>    Metadata,RAID1:         79.00GiB
>    Unallocated:             1.41TiB
> 
> /dev/sdb3, ID: 5
>    Device size:             9.06TiB
>    Device slack:            3.50KiB
>    Data,RAID1:              2.26TiB
>    Metadata,RAID1:         18.00GiB
>    System,RAID1:           32.00MiB
>    Unallocated:             6.79TiB
> 
> /dev/sdc2, ID: 3
>    Device size:             5.45TiB
>    Device slack:              0.00B
>    Data,RAID1:              4.00TiB
>    Metadata,RAID1:         77.00GiB
>    Unallocated:             1.38TiB
> 
> /dev/sdd3, ID: 6
>    Device size:             5.43TiB
>    Device slack:            3.50KiB
>    Data,RAID1:              2.03TiB
>    Metadata,RAID1:         18.00GiB
>    System,RAID1:           32.00MiB
>    Unallocated:             3.38TiB
> 
> /dev/sde3, ID: 4
>    Device size:            10.90TiB
>    Device slack:            3.50KiB
>    Data,RAID1:              7.96TiB
>    Metadata,RAID1:        146.00GiB
>    Unallocated:             2.79TiB
> 
> /dev/sdf3, ID: 7
>    Device size:             3.61TiB
>    Device slack:            3.50KiB
>    Data,RAID1:            235.00GiB
>    Unallocated:             3.38TiB
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-08-26  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26  8:58 btrfs-transacti -- change from be/4 to idle (?) Leszek Dubiel
2020-08-26  9:39 ` Qu Wenruo [this message]
2020-08-26 12:49   ` Leszek Dubiel
2020-08-26  9:47 ` Hans van Kranenburg

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=c4359a4d-ae86-1b12-1a33-9372fd81e84e@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=leszek@dubiel.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;
as well as URLs for NNTP newsgroup(s).