From: Josef Bacik <josef@redhat.com>
To: "Ken D'Ambrosio" <ken@jots.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Hardlinks-per-directory limit?
Date: Thu, 29 Jul 2010 09:50:52 -0400 [thread overview]
Message-ID: <20100729135046.GA2452@localhost.localdomain> (raw)
In-Reply-To: <7836277d97c74d44d8f2132e87db0b67.squirrel@webmail.jots.org>
On Thu, Jul 29, 2010 at 12:35:59AM -0400, Ken D'Ambrosio wrote:
> Hello, all. I'm thinking of rolling out a BackupPC server, and -- based
> on the strength of the recent Phoronix benchmarks
> (http://benchmarkreviews.com/index.php?option=com_content&task=view&id=11156&Itemid=23)
> -- had been strongly considering btrfs. But I do seem to recall that
> there was some sort of hardlinks-per-directory limitation, and BackupPC
> *loves* hardlinks. Would someone care to either remind me what the issue
> was, or reassure me that it's been rectified?
>
It's because we pack inode ref's into the same item, so once the item fills up
we can't add anymore refs. It's still a problem, not sure if/when its getting
fixed. Thanks,
Josef
next prev parent reply other threads:[~2010-07-29 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 4:35 Hardlinks-per-directory limit? Ken D'Ambrosio
2010-07-29 13:50 ` Josef Bacik [this message]
2010-08-01 17:43 ` David Brown
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=20100729135046.GA2452@localhost.localdomain \
--to=josef@redhat.com \
--cc=ken@jots.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).