From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Extremely slow metadata performance
Date: Thu, 5 Dec 2013 19:39:30 +0000 (UTC) [thread overview]
Message-ID: <pan$950f8$ef940490$829198f6$4f5f85c7@cox.net> (raw)
In-Reply-To: 52A0BD44.9030509@complete.org
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.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-12-05 19:39 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 [this message]
2013-12-07 9:22 ` Marc MERLIN
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='pan$950f8$ef940490$829198f6$4f5f85c7@cox.net' \
--to=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).