From: Brian Brunswick <brian.brunswick@gmail.com>
To: John Dong <jdong@ubuntu.com>
Cc: "jim owens" <jowens@hp.com>,
"Pär Andersson" <paran@lysator.liu.se>,
linux-btrfs@vger.kernel.org
Subject: Re: Mass-Hardlinking Oops
Date: Tue, 13 Oct 2009 10:08:38 +0100 [thread overview]
Message-ID: <6f680f6d0910130208m38c687aakc3cf4c0b355f699b@mail.gmail.com> (raw)
In-Reply-To: <DEABA03B-2896-484C-8DF9-F62E3E5AD342@ubuntu.com>
2009/10/12 John Dong <jdong@ubuntu.com>:
>
> On Oct 12, 2009, at 12:16 PM, jim owens wrote:
>
>> P=E4r 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.
>>> What is the reason for the limit, and is there any chance of increa=
sing
>>> it to something more reasonable as Mikhail suggested?
>>> For comparison I tried to create 200k hardlinks to the the same fil=
e in
>>> the same directory on btrfs, ext4, reiserfs and xfs:
>>
>> what real-world application uses and needs this many hard links?
>>
>> jim
>
> I don't think that's a good counterargument for why this is not a bug=
=2E
>
> Can't think of any off the top of my head for Linux, but definitely i=
n OS X
> Time Machine can easily create 200+ hardlinks.--
> 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
>
As a lurker, I've actually got a real-world example of something I do
that would probably hit this.
Its was hinted at before - web urls are sometimes rediculously long. I
run a web archiver on my router box that saves every http url I hit to
a file named after its url with a date appended. But then I
periodically run a de-duplicator on the saved stuff, which hard-links
together all files with the same contents (except empty ones)
I bet there are lots of examples that would exceed this limit within th=
ose dirs.
--=20
Brian_Brunswick____brian@ithil.org____Wit____Disclaimer____!Shortsig_ru=
les!
--
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-13 9:08 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
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 [this message]
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=6f680f6d0910130208m38c687aakc3cf4c0b355f699b@mail.gmail.com \
--to=brian.brunswick@gmail.com \
--cc=jdong@ubuntu.com \
--cc=jowens@hp.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=paran@lysator.liu.se \
/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