All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dipl.-Ing. Michael Niederle" <mniederle@gmx.at>
To: Goffredo Baroncelli <kreijack@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: severe hardlink bug
Date: Sun, 24 Jan 2010 14:08:37 +0100	[thread overview]
Message-ID: <20100124140837.5efcd526@simplux> (raw)
In-Reply-To: <201001240909.44753.kreijack@libero.it>

Hi, Goffredo!

> See this thread:

> Mass-Hardlinking Oops - http://thread.gmane.org/gmane.comp.file-
> systems.btrfs/3427

Sorry, I didn't find the thread myself - despite of massive googeling. :-(

The gentoo scenario however is a real world application - no artificial
situation, so it would be really nice to fix the hard link problem somewhere in
the future!

The problem will happen in all busybox-like scenarios - and long filenames are
not so rarely used.

Greetings, Michael

  parent reply	other threads:[~2010-01-24 13:08 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 [this message]
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=20100124140837.5efcd526@simplux \
    --to=mniederle@gmx.at \
    --cc=kreijack@gmail.com \
    --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.