All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt McKinnon <matt@techsquare.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-transacti hammering the system
Date: Fri, 1 Dec 2017 09:25:14 -0500	[thread overview]
Message-ID: <bb2cfbcb-31dd-715c-114f-59d574a2012b@techsquare.com> (raw)

Hi All,

Is there any way to figure out what exactly btrfs-transacti is chugging 
on?  I have a few file systems that seem to get wedged for days on end 
with this process pegged around 100%.  I've stopped all snapshots, made 
sure no quotas were enabled, turned on autodefrag in the mount options, 
tried manual defragging, kernel upgrades, yet still this brings my 
system to a crawl.

Network I/O to the system seems very tiny.  The only I/O I see to the 
disk is btrfs-transacti writing a couple M/s.

# time touch foo

real    2m54.303s
user    0m0.000s
sys     0m0.002s

# uname -r
4.12.8-custom

# btrfs --version
btrfs-progs v4.13.3

Yes, I know I'm a bit behind there...

-Matt




             reply	other threads:[~2017-12-01 14:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 14:25 Matt McKinnon [this message]
2017-12-01 14:52 ` btrfs-transacti hammering the system Hans van Kranenburg
2017-12-01 15:24   ` Matt McKinnon
2017-12-01 15:39     ` Hans van Kranenburg
2017-12-01 15:42       ` Matt McKinnon
2017-12-01 16:31       ` Matt McKinnon
2017-12-01 17:06         ` Hans van Kranenburg
2017-12-01 17:13           ` Andrei Borzenkov
2017-12-01 18:04             ` Austin S. Hemmelgarn
2017-12-02 19:42               ` Andrei Borzenkov
2017-12-01 17:34           ` Matt McKinnon
2017-12-01 17:57             ` Holger Hoffstätte
2017-12-01 18:24               ` Hans van Kranenburg
2017-12-01 19:07                 ` Matt McKinnon
2017-12-01 21:03                   ` Chris Murphy
2017-12-01 21:47           ` Duncan
2017-12-01 21:50             ` Matt McKinnon
2017-12-04 12:18               ` Austin S. Hemmelgarn
2017-12-04 14:10                 ` Duncan
2017-12-04 14:30                   ` Austin S. Hemmelgarn

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=bb2cfbcb-31dd-715c-114f-59d574a2012b@techsquare.com \
    --to=matt@techsquare.com \
    --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.