From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Konstantin Dmitriev <ksee.zelgadis@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: severe hardlink bug
Date: Mon, 30 Jul 2012 10:46:27 +0200 [thread overview]
Message-ID: <501649E3.6010600@jan-o-sch.net> (raw)
In-Reply-To: <loom.20120729T205902-38@post.gmane.org>
Hi Konstantin,
On Sun, July 29, 2012 at 21:02 (+0200), Konstantin Dmitriev wrote:
> Dipl.-Ing. Michael Niederle <mniederle <at> gmx.at> writes:
>
>> I reinstalled over 700 packages - plt-scheme beeing the only one failing due to
>> the btrfs link restriction.
>>
>
> I have hit the same issue - tried to run BackupPC with a pool on btrfs
> filesystem. After some time the error of "too many links (31)" appeared to me.
> Now I'm forced to migrate to some other filesystem...
Please give the patch set "btrfs: extended inode refs" by Mark Fasheh a try
(http://lwn.net/Articles/498226/). It eliminates the hard links per directory
limit (introducing a rather random, artificial limit of 64k instead).
-Jan
next prev parent reply other threads:[~2012-07-30 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 0:51 severe hardlink bug Michael Niederle
2010-01-24 8:09 ` Goffredo Baroncelli
2010-01-24 11:04 ` Stephan von Krawczynski
2010-01-25 15:45 ` Chris Mason
2010-01-24 13:08 ` Dipl.-Ing. Michael Niederle
2010-01-24 13:15 ` Goffredo Baroncelli
2010-01-24 13:27 ` Dipl.-Ing. Michael Niederle
2012-07-29 19:02 ` Konstantin Dmitriev
2012-07-29 19:13 ` C Anthony Risinger
2012-07-29 19:57 ` Konstantin Dmitriev
2012-07-30 9:36 ` Arnd Hannemann
2012-07-30 9:56 ` C Anthony Risinger
2012-07-30 9:59 ` Helmut Hullen
2012-07-30 8:46 ` Jan Schmidt [this message]
2012-08-08 6:37 ` Konstantin Dmitriev
2012-08-08 11:35 ` Chris Samuel
2012-07-30 17:38 ` Martin Steigerwald
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=501649E3.6010600@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=ksee.zelgadis@gmail.com \
--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.