linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Extremely slow metadata performance
Date: Sat, 7 Dec 2013 01:22:16 -0800	[thread overview]
Message-ID: <20131207092216.GL22683@merlins.org> (raw)
In-Reply-To: <pan$950f8$ef940490$829198f6$4f5f85c7@cox.net>

On Thu, Dec 05, 2013 at 07:39:30PM +0000, Duncan wrote:
> John Goerzen posted on Thu, 05 Dec 2013 11:52:04 -0600 as excerpted:
> 
> > Hello,
> > 
> > I have observed extremely slow metadata performance with btrfs. This may
> > be a bit of a nightmare scenario; it involves untarring a backup of
> > 1.6TB of backuppc data, which contains millions of hardlinks and much
> > data, onto USB 2.0 disks.
> 
> > Is this behavior known and expected?
> 
> Yes.  Btrfs doesn't do well with lots of hardlinks and indeed until 
> relatively recently had a hard-limit on the number of hardlinks possible 
> within a directory, that hardlink-heavy use-cases would regularly hit.  
> That was worked around, but there's an additional level of indirection 
> once the first level link-pool is filled, and you're not the first to 
> have observed that btrfs performance isn't the best in that sort of 
> scenario.  That's known.
> 
> Other filesystems will probably do quite a bit better for hardlink style 
> backups and other hardlink-heavy use-cases.  Either that, or consider 
> using btrfs, but with some other form of backup, possibly btrfs 
> snapshots, or COW reflinks.

Thanks for explaining this.

I'm one of those people who uses cp -al and rsync to do backups. Indeed
I should likely rework the flow to use subvolumes and snapshots.
You also mentioned reflinks, and it sounds like I can use
cp -a --reflink instead of cp -al.

Also, would the dedupe code in btrfs effectively allow for the same
thing after the fact if you use cp without --reflink? Is it stable
enough nowadays?

Thanks,
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

  reply	other threads:[~2013-12-07 14:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 17:52 Extremely slow metadata performance John Goerzen
2013-12-05 19:39 ` Duncan
2013-12-07  9:22   ` Marc MERLIN [this message]
2013-12-07 17:10     ` Kai Krakow
2013-12-05 23:41 ` Russell Coker
     [not found] ` <5930575.71jgM0vnzg@xev>
2013-12-06  4:48   ` John Goerzen
2013-12-06 14:35   ` John Goerzen

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=20131207092216.GL22683@merlins.org \
    --to=marc@merlins.org \
    --cc=1i5t5.duncan@cox.net \
    --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).