All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Goffredo Baroncelli <kreijack@gmail.com>,
	linux-btrfs@vger.kernel.org, mniederle@gmx.at
Subject: Re: severe hardlink bug
Date: Mon, 25 Jan 2010 10:45:04 -0500	[thread overview]
Message-ID: <20100125154504.GC331@think> (raw)
In-Reply-To: <20100124120432.41bd9b2d.skraw@ithnet.com>

On Sun, Jan 24, 2010 at 12:04:32PM +0100, Stephan von Krawczynski wrote:
> On Sun, 24 Jan 2010 09:09:44 +0100
> Goffredo Baroncelli <kreijack@gmail.com> wrote:
> 
> > On Sunday 24 January 2010, Michael Niederle wrote:
> > > I'm using btrfs with a kernel 2.6.32.2 (builtin) as the root file system of 
> > a
> > > Gentoo Linux installation.
> > > 
> > > While attempting to install the plt-scheme package a strange error about 
> > link
> > > counts occurred ([Error 31] Too many Links).
> > 
> > See this thread:
> > 
> > Mass-Hardlinking Oops - http://thread.gmane.org/gmane.comp.file-
> > systems.btrfs/3427
> > 
> > There is a limit of the number of hardlink for a file. The maximum number of 
> > the link depends by  name length.
> 
> Honestly, this dependency is braindead. How do the fs authors think an
> application programmer should judge how many hardlinks are possible for a
> certain fs ? This is a really bad design issue. Are we really in year 2010 ?

Yes, this was a design trade off to maintain the back links for the
file.  Keep in mind the limit is only per-directory, as long as you're
working between different directories you can have any many back links
as you want.

But, it's on the list to get fixed once raid5/6 are out of the way.

-chris


  reply	other threads:[~2010-01-25 15:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24  0:51 severe hardlink bug Michael Niederle
2010-01-24  8:09 ` Goffredo Baroncelli
2010-01-24 11:04   ` Stephan von Krawczynski
2010-01-25 15:45     ` Chris Mason [this message]
2010-01-24 13:08   ` Dipl.-Ing. Michael Niederle
2010-01-24 13:15     ` Goffredo Baroncelli
2010-01-24 13:27       ` Dipl.-Ing. Michael Niederle
2012-07-29 19:02         ` Konstantin Dmitriev
2012-07-29 19:13           ` C Anthony Risinger
2012-07-29 19:57             ` Konstantin Dmitriev
2012-07-30  9:36             ` Arnd Hannemann
2012-07-30  9:56               ` C Anthony Risinger
2012-07-30  9:59               ` Helmut Hullen
2012-07-30  8:46           ` Jan Schmidt
2012-08-08  6:37             ` Konstantin Dmitriev
2012-08-08 11:35               ` Chris Samuel
2012-07-30 17:38 ` Martin Steigerwald

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=20100125154504.GC331@think \
    --to=chris.mason@oracle.com \
    --cc=kreijack@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mniederle@gmx.at \
    --cc=skraw@ithnet.com \
    /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.