From: David Brown <btrfs@davidb.org>
To: "Ken D'Ambrosio" <ken@jots.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Hardlinks-per-directory limit?
Date: Sun, 1 Aug 2010 10:43:23 -0700 [thread overview]
Message-ID: <201008011043.23048.btrfs@davidb.org> (raw)
In-Reply-To: <7836277d97c74d44d8f2132e87db0b67.squirrel@webmail.jots.org>
On Wednesday 28 July 2010, Ken D'Ambrosio said:
> 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?
btrfs has a limit on the number of hardlinks that can exist in the
same directory. I don't believe that BackupPC will create any more
hardlinks in a given directory than are already in the filesystem you
are backing up. It uses hardlinks between directories for files that
haven't changed.
David
prev parent reply other threads:[~2010-08-01 17:43 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
2010-08-01 17:43 ` David Brown [this message]
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=201008011043.23048.btrfs@davidb.org \
--to=btrfs@davidb.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.