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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
