From: Sami Liedes <sami.liedes@iki.fi>
To: linux-btrfs@vger.kernel.org
Subject: Will big metadata blocks fix # of hardlinks?
Date: Sat, 26 May 2012 21:22:12 +0300 [thread overview]
Message-ID: <20120526182211.GA16059@sli.dy.fi> (raw)
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
Hi!
I see that Linux 3.4 supports bigger metadata blocks for btrfs.
Will using them allow a bigger number of hardlinks on a single file
(i.e. the bug that has bitten at least git users on Debian[1,2], and
BackupPC[3])? As far as I understand correctly, the problem has been
that the hard links are stored in the same metadata block with some
other metadata, so the size of the block is an inherent limitation?
If so, I think it would be worth for me to try Btrfs again :)
Sami
[1] http://permalink.gmane.org/gmane.comp.file-systems.btrfs/13603
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642603
[3] https://bugzilla.kernel.org/show_bug.cgi?id=15762
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-05-26 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 18:22 Sami Liedes [this message]
2012-05-29 13:09 ` Will big metadata blocks fix # of hardlinks? Martin
2012-05-29 13:23 ` Hugo Mills
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=20120526182211.GA16059@sli.dy.fi \
--to=sami.liedes@iki.fi \
--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).