linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Guenter <bruce@untroubled.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Slow snapshot deletion
Date: Mon, 1 Aug 2011 16:26:04 -0600	[thread overview]
Message-ID: <20110801222604.GA3529@untroubled.org> (raw)
In-Reply-To: <1311884805-sup-7662@shiny>

[-- Attachment #1: Type: text/plain, Size: 894 bytes --]

On Thu, Jul 28, 2011 at 04:28:04PM -0400, Chris Mason wrote:
> The slow performance is probably coming from reading in the metadata
> associated with the snapshot extents.  The new readahead extentions from
> Arne should help once we've adapted them to it.  The easiest way to make
> sure is to hit sysrq-w a few times while it is slow (or run a patched
> latencytop).

We shut down the rsync backups for now, and are waiting for the
snapshots to complete deletion so we can unmount the filesystem to
reboot (missing kernel options for latencytop).  In the mean time I hit
SysRq-W quite a number of times, and nothing is showing up in kernel
messages.  However, btrfs-cleaner and/or btrfs-transaction (sometimes
both, sometimes just one) have been running high in top, taking up all
the CPU time.

-- 
Bruce Guenter <bruce@untroubled.org>                http://untroubled.org/

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2011-08-01 22:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 20:04 Slow snapshot deletion Bruce Guenter
2011-07-28 20:28 ` Chris Mason
2011-07-28 20:51   ` Chris Mason
2011-08-04 16:35     ` Bruce Guenter
2011-08-11 15:04       ` Bruce Guenter
2011-08-12  0:40         ` Simon Kirby
2011-08-12 18:21           ` Bruce Guenter
2011-08-12 18:26             ` Simon Kirby
2011-08-01 22:26   ` Bruce Guenter [this message]
2011-08-01 22:41     ` cwillu
2011-08-01 22:59       ` Bruce Guenter
2011-08-02  0:29         ` Chris Mason

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=20110801222604.GA3529@untroubled.org \
    --to=bruce@untroubled.org \
    --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).