linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ken D'Ambrosio" <ken@jots.org>
To: linux-btrfs@vger.kernel.org
Subject: Hardlinks-per-directory limit?
Date: Thu, 29 Jul 2010 00:35:59 -0400 (EDT)	[thread overview]
Message-ID: <7836277d97c74d44d8f2132e87db0b67.squirrel@webmail.jots.org> (raw)

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?

Thanks!

-Ken


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


             reply	other threads:[~2010-07-29  4:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29  4:35 Ken D'Ambrosio [this message]
2010-07-29 13:50 ` Hardlinks-per-directory limit? Josef Bacik
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=7836277d97c74d44d8f2132e87db0b67.squirrel@webmail.jots.org \
    --to=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).