From: Goffredo Baroncelli <kreijack@alice.it>
To: linux-btrfs@vger.kernel.org
Subject: Re: Mass-Hardlinking Oops
Date: Mon, 12 Oct 2009 19:09:56 +0200 [thread overview]
Message-ID: <200910121909.56545.kreijack@alice.it> (raw)
In-Reply-To: <4AD35667.3020103@hp.com>
On Monday 12 October 2009, jim owens wrote:
> P=C3=A4r Andersson wrote:
> > I just ran into the max hard link per directory limit, and remember=
ed
> > this thread. I get EMLINK when trying to create more than 311 (not =
272)
> > links in a directory, so at least the BUG() is fixed.
> >=20
> > What is the reason for the limit, and is there any chance of increa=
sing
> > it to something more reasonable as Mikhail suggested?
> >=20
> > For comparison I tried to create 200k hardlinks to the the same fil=
e in
> > the same directory on btrfs, ext4, reiserfs and xfs:
>=20
> what real-world application uses and needs this many hard links?
>=20
> jim
=46or me 311 "hard link to the same file under the same directory" limi=
t is not=20
so high.
I don't know a software which need so many hard links. But it easy to f=
ind=20
some similar cases.
=46or example under my "/usr/bin" I have 478 _"soft links"_ to _differe=
nt_=20
files.
$ find /usr/bin/ -type l | wc -l
478
When a directory is created, its ".." entry is a hard link to the "pare=
nt"=20
directory. For example the /usr/share/doc directory has 2828 "hard link=
s"=20
because it has 2826 children directories.
$ ls -ld /usr/share/doc
drwxr-xr-x 2828 root root 12288 2009-08-20 19:03 /usr/share/doc
$ ls -ld /usr/share/* | egrep "^d" | wc -l
2826
These cases are different cases. But the 311 "hard link to the same fil=
e under=20
the same directory" limit may be too strong. Not now but in the next fo=
rmat=20
change I think that it would be useful to remove this limit.
BR
Goffredo
--=20
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijackATinw=
ind.it>
Key fingerprint =3D 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-12 17:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 13:16 Mass-Hardlinking Oops Raskin Michael
2009-08-03 14:57 ` Chris Mason
2009-08-03 15:00 ` Tomasz Chmielewski
2009-08-03 20:01 ` Mikhail Raskin
2009-10-11 15:05 ` Pär Andersson
2009-10-11 22:43 ` Yan, Zheng
2009-10-12 8:07 ` Tomasz Chmielewski
2009-10-12 12:47 ` Chris Mason
2009-10-13 7:07 ` Florian Weimer
2009-10-13 7:28 ` Yan, Zheng
2009-10-14 0:29 ` Matteo Frigo
2009-10-15 17:55 ` Tracy Reed
2009-10-15 18:27 ` Tomasz Chmielewski
2009-10-15 19:15 ` Oystein Viggen
2009-10-16 22:17 ` Pär Andersson
2009-10-12 16:16 ` jim owens
2009-10-12 17:09 ` Goffredo Baroncelli [this message]
2009-10-12 18:07 ` jim owens
2009-10-12 17:42 ` John Dong
2009-10-12 18:17 ` jim owens
2009-10-12 20:04 ` Chris Mason
2009-10-12 21:51 ` berk walker
2009-10-13 0:31 ` Claudio Martins
2009-10-13 3:42 ` Anthony Roberts
2009-10-13 9:08 ` Brian Brunswick
2009-10-13 17:45 ` Zach Brown
2009-10-13 20:03 ` Chris Mason
2009-10-13 20:55 ` Zach Brown
2009-10-12 20:50 ` Tomasz Chmielewski
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=200910121909.56545.kreijack@alice.it \
--to=kreijack@alice.it \
--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