linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-btrfs@vger.kernel.org
Subject: Too many links
Date: Mon, 28 Feb 2011 11:20:59 -0500	[thread overview]
Message-ID: <ikgi1c$j83$1@dough.gmane.org> (raw)

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

In doing some btrfs testing (on 2.6.32-22-generic and 2.6.35-24-generic)
I seem to have come across a limitation in how many links I can have in
a single directory.  I hit the EMLINK trying to create the 72nd link
(with rsync, replicating from a source directory fwiw).  The source
directory of the rsync has 2400 links that need to be replicated on btrfs.

The most recent info I can find is a thread from mid-2010:

http://www.spinics.net/lists/linux-btrfs/msg05619.html

I guess this is still a limitation?  Is the future of a fix still as
unclear as it was back in July 2010?

Thanx,
b.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

                 reply	other threads:[~2011-02-28 16:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='ikgi1c$j83$1@dough.gmane.org' \
    --to=brian@interlinx.bc.ca \
    --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).