From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Chris Mason <chris.mason@oracle.com>,
Raskin Michael <raskin@mccme.ru>,
linux-btrfs@vger.kernel.org
Subject: Re: Mass-Hardlinking Oops
Date: Mon, 03 Aug 2009 17:00:08 +0200 [thread overview]
Message-ID: <4A76FB78.5000207@wpkg.org> (raw)
In-Reply-To: <20090803145741.GC3765@think>
Chris Mason wrote:
> On Sat, Aug 01, 2009 at 05:16:11PM +0400, Raskin Michael wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> This is distinct from the old mass-symlinking warnings. I run a program
>> which promised to hardlink all the same-content files on the partition.
>> The failure occured reasonably quickly...
>
> As Yan said on IRC there's a limit to the number of hardlinks per file
> in a given directory. We clearly need to change this from BUG() to
> return a nice error.
BTW, what limit is that?
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2009-08-03 15:00 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 [this message]
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
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=4A76FB78.5000207@wpkg.org \
--to=mangoo@wpkg.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=raskin@mccme.ru \
/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.