From: Josef Bacik <josef@redhat.com>
To: John Fremlin <john@fremlin.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS should increase the hard-link in the same directory limit
Date: Mon, 22 Aug 2011 10:54:21 -0400 [thread overview]
Message-ID: <4E526D9D.8010202@redhat.com> (raw)
In-Reply-To: <874o1aztkm.fsf-genuine-vii@john.fremlin.org>
On 08/21/2011 11:13 AM, John Fremlin wrote:
> It seems a priori that there should not be any need for more than 256
> names for the same file in the same directory. However, the GNUS
> mailreader's nnmaildir backend uses hardlinks to mark email messages
> read, and instead of creating a separate inode for each marked
> message, uses a hardlink to a single markfile. This means that there
> maybe thousands of hardlinks to the same inode in a single directory.
>
> This is not unreasonable as the obvious workaround is to wastefully
> create more inodes.
>
> This restriction causes btrfs-convert 0.19 to crash out with a segfault and
> no helpful message: something like btrfs-convert: segfault at
> ffffffffcfb25fb9 ip 000000000040f9f1 sp 00007fffddefb398 error 6 in
> btrfs-convert[400000+21000].
>
> Is there any plan to alleviate this unfortunate limit (or at least make
> btrfs-convert give the location of the file which causes it to fail?).
It's a disk format change, something we don't do lightly.
Josef
next prev parent reply other threads:[~2011-08-22 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 15:13 BTRFS should increase the hard-link in the same directory limit John Fremlin
2011-08-21 22:05 ` James Cloos
2011-08-23 15:29 ` David Nicol
2011-08-22 14:54 ` Josef Bacik [this message]
2011-08-22 16:05 ` John Fremlin
2011-08-22 16:06 ` Josef Bacik
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=4E526D9D.8010202@redhat.com \
--to=josef@redhat.com \
--cc=john@fremlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.