From: Anthony Roberts <btrfs-devel@arbitraryconstant.com>
To: <nicollet@jeru.org>
Cc: <linux-btrfs@vger.kernel.org>, <cbarratt@users.sourceforge.net>
Subject: Re: Number of hard links limit
Date: Mon, 02 Aug 2010 12:31:12 -0600 [thread overview]
Message-ID: <4ad406cb8ee6c52747b67b4c79a6d7dd@smtp.arbitraryconstant.com> (raw)
In-Reply-To: <20100802130556.GF30325@jeru.org>
On Mon, 2 Aug 2010 15:05:56 +0200, Xavier Nicollet <nicollet@jeru.org>
wrote:
> Le 02 ao=C3=BBt 2010 =C3=A0 14:40, Sami Liedes a =C3=A9crit:
>> [BTRFS supports only 256 hard-links per directory ...] but if it
>> indeed needs a disk format change, I think this should be considered
>> before the format is set in stone. I won't personally lose my sleep =
if
>> this is not fixed - I can use other filesystems for backuppc and oth=
er
>> similar systems,=20
>=20
> Wouldn't it be even better to actually patch BackupPC to handle btrfs
> snapshots and COW (bcp) ?
That's not the only application impacted by this.
Also, I think it's unrealistic to expect everyone else to code to
BTRFS-specific ioctls when there's other filesystems and other platform=
s to
worry about. It would also be nice if we could tar/rsync/whatever betwe=
en
BTRFS and something else like ext3 or some other OS entirely, without
archiving tools either blowing up or requiring application-specific
knowledge of how to convert dedups to hard links and back.
Also, I believe it's not strictly 256 links, it's dependent on the leng=
th
of the names.
I recall Chris posting something about being able to fix this without a
format change, though it wasn't a priority yet.
-Anthony
--
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 18:31 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 [this message]
2010-08-02 19:56 ` Michael Niederle
2010-08-02 20:43 ` Roberto Ragusa
2010-08-02 22:22 ` Oystein Viggen
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=4ad406cb8ee6c52747b67b4c79a6d7dd@smtp.arbitraryconstant.com \
--to=btrfs-devel@arbitraryconstant.com \
--cc=cbarratt@users.sourceforge.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=nicollet@jeru.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).