From: Arnd Hannemann <arnd@arndnet.de>
To: nspmangalore@gmail.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: hard links
Date: Wed, 04 Apr 2012 21:39:39 +0200 [thread overview]
Message-ID: <4F7CA37B.50006@arndnet.de> (raw)
In-Reply-To: <4F7CA218.5070902@gmail.com>
Hi Shyam,
Am 04.04.2012 21:33, schrieb Shyam Prasad N:
> 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?
>>
> What do you mean by 'used all available inode space'? What did you do exactly?
I created hard links of a file in the same directory until no additional one
can be created.
Eg.:
touch a
for i in {1..1000}; do ln a $i; done;
Best regards
Arnd
next prev parent reply other threads:[~2012-04-04 19:39 UTC|newest]
Thread overview: 6+ 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
2012-04-04 19:39 ` Arnd Hannemann [this message]
2012-04-04 19:53 ` Hugo Mills
2012-04-04 20:12 ` Arnd Hannemann
2012-04-04 20:57 ` Zach Brown
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=4F7CA37B.50006@arndnet.de \
--to=arnd@arndnet.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=nspmangalore@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).