From: Chris Mason <chris.mason@oracle.com>
To: jim owens <jowens@hp.com>
Cc: "John Dong" <jdong@ubuntu.com>,
"Pär Andersson" <paran@lysator.liu.se>,
linux-btrfs@vger.kernel.org
Subject: Re: Mass-Hardlinking Oops
Date: Mon, 12 Oct 2009 16:04:42 -0400 [thread overview]
Message-ID: <20091012200442.GA8830@think> (raw)
In-Reply-To: <4AD372A7.2020907@hp.com>
On Mon, Oct 12, 2009 at 02:17:11PM -0400, jim owens wrote:
> John Dong wrote:
> >
> >I don't think that's a good counterargument for why this is not a bug.
>
> it is not a "bug". hard links are not a required feature of all
> filesystems nor is a defined large number required for those with
> hard links.
>
> >Can't think of any off the top of my head for Linux, but
> >definitely in OS X Time Machine can easily create 200+ hardlinks.
>
> so 311 is 50% than the app uses... plenty of growth.
Just to clarify again, the max link count on btrfs is 2^32. The lower
limit is only in place on links to the same file in the same directory.
Jim is correct about the link count on subdirs being unrelated. The
link count on btrfs directories is always one.
-chris
next prev parent reply other threads:[~2009-10-12 20:04 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 [this message]
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=20091012200442.GA8830@think \
--to=chris.mason@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