On Fri, May 10, 2013 at 01:54:24PM +0200, Julian Andres Klode wrote: > On Fri, May 10, 2013 at 11:56:19AM +0200, Uli Martens wrote: > > I'm running into problems running hardlink on my btrfs file system, at > > around 200 hardlinks per file: [...] > > Please provide a flag limiting the maximum number of hardlinks, and perhaps > > a > > way to make hardlink figure out the limits by itself.
> The version in experimental works around this problem (by linking everything > to the next best file instead), but still displays a warning. It seems I > forgot to mention this in the changelog. This means that you should only > see the warning *once*. Damn. I even downloaded experimental's version and looked into the changelog, but didn't install it and actually check it. :) Now I did, and yes, for 1000 copies of the same file, I get five inodes with ~200 links each, which is what I wanted, and four warning messages on this run, which is not great but okay. But on following runs with unchanged files, I *still* get these four warning messages. I think the best way would be to show a warning like WARNING: file system limit on hard links reached for some files once when that happens instead of for each inode tried, and additionally to not show that warning when some flag is given, perhaps -l --ignore-link-limit I'd offer bonus points in form of free beverages for having that option persistant, but as hardlink doesn't have a config file, that's probably overkill. Perhaps the other way, ignoring ELINK all the time and only showing it with -vv (but not "normal" --verbose) is more userfriendly? Thank you for your work, youam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
