From: Oystein Viggen <oysteivi@tihlde.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Number of hard links limit
Date: Tue, 03 Aug 2010 00:22:14 +0200 [thread overview]
Message-ID: <0362zshcyx.fsf@msgid.viggen.net> (raw)
In-Reply-To: 4C572DDC.5050108@robertoragusa.it
* [Roberto Ragusa]=20
> That means it would not work for my backup server.
> At 4 backups per day, failure for filenames with 45 characters after =
just
> one year.
IIRC, the limit on hard links is per directory. That is, if you put
each hard link into its own directory, there's basically no limit to th=
e
amount of hard links you can make to one file.
Thus, many generations of backup with BackupPC shouldn't trigger the
problem, as each generation is stored in its own directory tree. The
problem appears when your source data has many identical files in the
same directory, since these would be deduplicated as hard links to the
same file in the backup pool.
=D8ystein
--=20
This message was generated by a horde of attack elephants armed with PR=
NGs.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-02 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 11:40 Number of hard links limit Sami Liedes
2010-08-02 13:05 ` Xavier Nicollet
2010-08-02 18:31 ` Anthony Roberts
2010-08-02 19:56 ` Michael Niederle
2010-08-02 20:43 ` Roberto Ragusa
2010-08-02 22:22 ` Oystein Viggen [this message]
2010-08-06 11:30 ` Sami Liedes
2010-08-06 13:46 ` Chris Mason
2010-08-08 12:32 ` Roberto Ragusa
2011-10-12 17:34 ` Martin Steigerwald
2011-11-08 21:23 ` Sami Liedes
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=0362zshcyx.fsf@msgid.viggen.net \
--to=oysteivi@tihlde.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).