All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hullen@t-online.de (Helmut Hullen)
To: linux-btrfs@vger.kernel.org
Subject: Re: severe hardlink bug
Date: 30 Jul 2012 11:59:00 +0200	[thread overview]
Message-ID: <CDqX2gsuCXB@helmut.hullen.de> (raw)
In-Reply-To: <50165584.70707@arndnet.de>

Hallo, Arnd,

Du meintest am 30.07.12:

>> btrfs only fails when you have hundreds of hardlinks to the same
>> file in the *same* directory ... certainly not a standard use case.

> Actually, "hundreds of hardlinks" is certainly over optimistic.
> In my testing 15 links in the same directory were enough to get
> the "Too many links" error. It depends on the length of the file
> name of the hardlinks.

And then I may get problems with my favourite backup program  
"rsnapshot"; it uses hard links, and my backups often have more than 20  
hard links to 1 file. Sometimes about 80 characters long.

Viele Gruesse!
Helmut

  parent reply	other threads:[~2012-07-30 10:25 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
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 [this message]
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=CDqX2gsuCXB@helmut.hullen.de \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.de \
    --cc=linux-btrfs@vger.kernel.org \
    /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.