From: Shyam Prasad N <nspmangalore@gmail.com>
To: Arnd Hannemann <arnd@arndnet.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: hard links
Date: Thu, 05 Apr 2012 01:03:44 +0530 [thread overview]
Message-ID: <4F7CA218.5070902@gmail.com> (raw)
In-Reply-To: <4F7C78FE.2020508@arndnet.de>
On 04/04/2012 10:08 PM, Arnd Hannemann wrote:
> Hi,
>
> today I experimented with hard links on btrfs and by this used all available inode space of a file.
> Interestingly if this happens even a rename of such an filename to an _equal length_ filename
> fails:
>
> arnd@kallisto:/mnt/btrfs/tmp$ mv a b
> mv: cannot move `a' to `b': Too many links
>
> Is this expected behavior?
> There should be no reason to let this particular case fail?
>
> Best regards,
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Arnd,
What do you mean by 'used all available inode space'? What did you do
exactly?
Thanks,
Shyam
next prev parent reply other threads:[~2012-04-04 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 16:38 hard links Arnd Hannemann
2012-04-04 19:33 ` Shyam Prasad N [this message]
2012-04-04 19:39 ` Arnd Hannemann
2012-04-04 19:53 ` Hugo Mills
2012-04-04 20:12 ` Arnd Hannemann
2012-04-04 20:57 ` Zach Brown
-- strict thread matches above, loose matches on Subject: below --
2010-02-02 21:05 Slides from Ceph talk at linux.conf.au? Craig Dunwoody
2010-02-02 21:43 ` Sage Weil
2010-02-05 0:17 ` Hard links Chris Dunlop
2010-02-05 20:34 ` Sage Weil
2010-02-07 1:09 ` Chris Dunlop
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=4F7CA218.5070902@gmail.com \
--to=nspmangalore@gmail.com \
--cc=arnd@arndnet.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.