From: Arnd Hannemann <arnd@arndnet.de>
To: C Anthony Risinger <anthony@xtfx.me>
Cc: Konstantin Dmitriev <ksee.zelgadis@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: severe hardlink bug
Date: Mon, 30 Jul 2012 11:36:04 +0200 [thread overview]
Message-ID: <50165584.70707@arndnet.de> (raw)
In-Reply-To: <CAGAVQTFADbS95X9NbtOBx7m=R3tXB1exauQtSpPfBc2m72tNqg@mail.gmail.com>
Am 29.07.2012 21:13, schrieb C Anthony Risinger:
> On Sun, Jul 29, 2012 at 2:02 PM, Konstantin Dmitriev
> <ksee.zelgadis@gmail.com> 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...
>
> btrfs only fails when you have hundreds of hardlinks to the same file
> in the *same* directory ... certainly not a standard use case.
Actually, "hundreds of hardlinks" is certainly over optimistic.
In my testing 15 links in the same directory were enough to get
the "Too many links" error. It depends on the length of the file
name of the hardlinks.
Best regards
Arnd
next prev parent reply other threads:[~2012-07-30 9:36 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 [this message]
2012-07-30 9:56 ` C Anthony Risinger
2012-07-30 9:59 ` Helmut Hullen
2012-07-30 8:46 ` Jan Schmidt
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=50165584.70707@arndnet.de \
--to=arnd@arndnet.de \
--cc=anthony@xtfx.me \
--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 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).