From: Donald Pearson <donaldwhpearson@gmail.com>
To: Marc MERLIN <marc@merlins.org>
Cc: sander@humilis.net, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Anyone tried out btrbk yet?
Date: Mon, 20 Jul 2015 00:15:26 -0500 [thread overview]
Message-ID: <CAC=t97CcemZzBjABSLS5etSF6B-67SvwL25q62hxv2de3zLPbw@mail.gmail.com> (raw)
In-Reply-To: <20150715214913.GG5274@merlins.org>
I'm starting to think there's something wrong with creating and
removing snapshots that leaves btrfs-cleaner either locked up or
nearly so. If the btrfs-cleaner process was hard-disk limited I
should be seeing some HDD I/O to coincide but I don't.
So far btrfs-cleaner is has been using lots of CPU for 1900+ hours and
my disk I/O is basically idle. My hourly snaps via cronjob stalled 11
hours ago.
Otherwise attempts to read/write to the filesystem appear to be
perfectly normal.
[root@san01 virtual_machines]# ps aux | grep btrfs-cleaner
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1292 0.0 0.0 0 0 ? S Jul16
0:01 [btrfs-cleaner]
root 5796 0.0 0.0 0 0 ? S Jul16
0:00 [btrfs-cleaner]
root 6005 21.3 0.0 0 0 ? S Jul16
943:34 [btrfs-cleaner]
root 14040 43.3 0.0 0 0 ? R Jul16
1916:05 [btrfs-cleaner]
[root@san01 virtual_machines]# ls -lah /run | grep backup
-rw-r--r-- 1 root root 11 Jul 20 00:00 backup.home.daily
-rw-r--r-- 1 root root 11 Jul 20 00:00 backup.root.daily
-rw-r--r-- 1 root root 11 Jul 20 00:01 backup.store.daily
-rw-r--r-- 1 root root 11 Jul 19 13:00 backup.store.hourly
-rw-r--r-- 1 root root 11 Jul 20 00:01 backup.virtual_machines.daily
-rw-r--r-- 1 root root 11 Jul 19 13:00
backup.virtual_machines.hourly
[root@san01 virtual_machines]# date
Mon Jul 20 00:14:05 CDT 2015
On Wed, Jul 15, 2015 at 4:49 PM, Marc MERLIN <marc@merlins.org> wrote:
> On Wed, Jul 15, 2015 at 01:02:29PM -0500, Donald Pearson wrote:
>> BTW, is anybody else experiencing btrfs-cleaner consuming heavy
>> resources for a very long time when snapshots are removed?
>
> Yes, that's normal. It spends a long time to reclaim blocks and free
> them, especially if they are on a hard drive and not SSD.
>
> Marc
> --
> "A mouse is a device used to point at the xterm you want to type in" - A.S.R.
> Microsoft is to operating systems ....
> .... what McDonalds is to gourmet cooking
> Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2015-07-20 5:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 12:26 Anyone tried out btrbk yet? Martin Steigerwald
2015-07-09 17:12 ` Henri Valta
2015-07-09 17:17 ` Marc MERLIN
2015-07-10 1:35 ` Donald Pearson
2015-07-10 1:38 ` Donald Pearson
2015-07-10 4:02 ` Paul Harvey
2015-07-10 10:46 ` Axel Burri
2015-07-12 3:55 ` Marc MERLIN
2015-07-13 0:42 ` Marc MERLIN
2015-07-15 0:03 ` Paul Harvey
2015-07-15 3:14 ` Marc MERLIN
2015-07-15 8:00 ` Sander
2015-07-15 14:42 ` Donald Pearson
2015-07-15 18:02 ` Donald Pearson
2015-07-15 21:49 ` Marc MERLIN
2015-07-20 5:15 ` Donald Pearson [this message]
2015-07-20 8:28 ` Duncan
2015-07-20 13:33 ` Donald Pearson
2015-07-21 9:29 ` Duncan
2015-07-22 1:29 ` Donald Pearson
2015-07-25 13:27 ` Donald Pearson
2015-07-26 5:39 ` Duncan
2015-07-15 21:48 ` Marc MERLIN
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='CAC=t97CcemZzBjABSLS5etSF6B-67SvwL25q62hxv2de3zLPbw@mail.gmail.com' \
--to=donaldwhpearson@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.org \
--cc=sander@humilis.net \
/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.