From: "Michael Niederle" <mniederle@gmx.at>
To: linux-btrfs@vger.kernel.org
Subject: severe hardlink bug
Date: Sun, 24 Jan 2010 01:51:38 +0100 [thread overview]
Message-ID: <20100124015138.092c4959@simplux> (raw)
I'm using btrfs with a kernel 2.6.32.2 (builtin) as the root file system of a
Gentoo Linux installation.
While attempting to install the plt-scheme package a strange error about link
counts occurred ([Error 31] Too many Links).
I was able to create a simple scenario to reproduce the error:
Create an empty directory and run the following script within the directory:
#!/bin/bash
echo "abc" >.tab-snip-class_scrbl.dep._portage_merge_.9766
for x in $(seq 80)
do echo $x; ln .tab-snip-class_scrbl.dep._portage_merge_.9766 \
.tab-snip-class_scrbl.dep._portage_merge_.9766.$x; done
(The names are taken from the original Gentoo package.)
When I run this script the first 66 links are created properly. All further
link creations fail:
...
63
64
65
66
67
ln: creating hard link to `.tab-snip-class_scrbl.dep._portage_merge_.9766': Too
many links 68
ln: creating hard link to `.tab-snip-class_scrbl.dep._portage_merge_.9766': Too
many links 69
ln: creating hard link to `.tab-snip-class_scrbl.dep._portage_merge_.9766': Too
many links 70
ln: creating hard link to `.tab-snip-class_scrbl.dep._portage_merge_.9766': Too
many links
...
I was able to reproduce the bug independently on two different machines.
During earlier tests I determined that filename length has an effect as well as
the link count.
Greetings, Michael
next reply other threads:[~2010-01-24 0:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 0:51 Michael Niederle [this message]
2010-01-24 8:09 ` severe hardlink bug 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
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=20100124015138.092c4959@simplux \
--to=mniederle@gmx.at \
--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.