From: Zach Brown <zach.brown@oracle.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:45:43 -0700 [thread overview]
Message-ID: <4AD4BCC7.3060204@oracle.com> (raw)
In-Reply-To: <DEABA03B-2896-484C-8DF9-F62E3E5AD342@ubuntu.com>
>>> this thread. I get EMLINK when trying to create more than 311 (not 272)
>>> links in a directory
>>
>> what real-world application uses and needs this many hard links?
>
> I don't think that's a good counterargument for why this is not a bug.
I strongly agree. Our ignorance of users operating inside existing
limits of existing file systems shouldn't justify tightening those limits.
Sure, this is a weird corner case. But given how early btrfs is in the
deployment stage, it seems worth changing the format to get rid of this
risk of teaching people to question their expectation that btrfs will
just work in environments that previous linux file systems worked in.
- z
next prev parent reply other threads:[~2009-10-13 17:45 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
2009-10-13 17:45 ` Zach Brown [this message]
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=4AD4BCC7.3060204@oracle.com \
--to=zach.brown@oracle.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