From: Arnd Hannemann <arnd@arndnet.de>
To: linux-btrfs@vger.kernel.org
Subject: hard links
Date: Wed, 04 Apr 2012 18:38:22 +0200 [thread overview]
Message-ID: <4F7C78FE.2020508@arndnet.de> (raw)
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
next reply other threads:[~2012-04-04 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 16:38 Arnd Hannemann [this message]
2012-04-04 19:33 ` hard links Shyam Prasad N
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
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=4F7C78FE.2020508@arndnet.de \
--to=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 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).