linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sami Liedes <sliedes@cc.hut.fi>
To: linux-btrfs@vger.kernel.org
Subject: Number of hard links limit
Date: Mon, 2 Aug 2010 14:40:46 +0300	[thread overview]
Message-ID: <20100802114046.GA29926@lh.kyla.fi> (raw)

[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]

Hi,

There's been discussion before on this list on the very small number
of hard links supported by btrfs.[1][2] In those threads, an often
asked question has been if there's a real world use case the limit
breaks. Also it has been pointed out that a fix for this would need a
disk format change.

As discussed in bug #15762 [3], there are certainly real-world use
cases this limitation breaks. I don't usually like to bring up my pet
bugs on mailing lists, and I'm sorry for doing it here, 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 other
similar systems, although I'd be disappointed to see a production
backup system unexpectedly fail because of this - just that I think
it's better to think about this before things are set in stone.

I'd venture to guess that if I have hit this limit with the very small
amount of btrfs use I've done, thousands of others are going to hit it
when btrfs is the default filesystem of distributions.

	Sami


[1] http://comments.gmane.org/gmane.comp.file-systems.btrfs/4589
[2] http://thread.gmane.org/gmane.comp.file-systems.btrfs/3427
[3] https://bugzilla.kernel.org/show_bug.cgi?id=15762

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2010-08-02 11:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 11:40 Sami Liedes [this message]
2010-08-02 13:05 ` Number of hard links limit 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
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=20100802114046.GA29926@lh.kyla.fi \
    --to=sliedes@cc.hut.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).