From: Chris Mason <chris.mason@oracle.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Bruce Guenter <bruce@untroubled.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Slow snapshot deletion
Date: Thu, 28 Jul 2011 16:51:24 -0400 [thread overview]
Message-ID: <1311886250-sup-5126@shiny> (raw)
In-Reply-To: <1311884805-sup-7662@shiny>
Excerpts from Chris Mason's message of 2011-07-28 16:28:04 -0400:
> Excerpts from Bruce Guenter's message of 2011-07-28 16:04:45 -0400:
> >
> > At work we have a backup server system running btrfs. The main backup
> > pool is a 1.3TB partition (on LVM). Every night, a series of backups
> > are done with rsync, with each backup onto a separate subvolume, and a
> > snapshot made of each backup. Compression is used to minimize disk
> > space used.
> >
> > When the system was first provisioned, all the operations ran
> > impressively fast, but now it is almost unusably slow. It has taken 2
> > days to delete snapshots that recovered 30GB of space, and some of the
> > backups are taking longer than 24 hours to complete.
> >
> > Is there any way to monitor the progress of the snapshot deletions?
> >
> > What could be causing it to run so slow?
> >
> > What could we do to speed things up?
> >
> > Kernel is 2.6.39-gentoo-r3. It was last rebooted 2 days ago, and
> > rebooting does not seem to improve the situation. Mount options
> > according to /proc are "rw,nosuid,noatime,nodiratime,compress=zlib,noacl"
> > btrfs filesystem df shows:
> >
> > Data: total=1.15TB, used=1.10TB
> > System, DUP: total=8.00MB, used=184.00KB
> > System: total=4.00MB, used=0.00
> > Metadata, DUP: total=49.38GB, used=31.59GB
> > Metadata: total=8.00MB, used=0.00
> >
>
> 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).
Sorry, hit send too soon. Here is the latencytop patch, after you
recompile run latencytop -c for a few minutes. Send the output here.
http://oss.oracle.com/~mason/latencytop.patch
-chris
next prev parent reply other threads:[~2011-07-28 20:51 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 [this message]
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
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=1311886250-sup-5126@shiny \
--to=chris.mason@oracle.com \
--cc=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).