🚀 go-pugleaf

>1) Use the distributed backup scripts.  These never dump more than one
>filesystem per archive, and avoid the problem.  Since there are other

These are nice, but don't really solve the fundamental problem and
probably shouldn't be considered a solution of any sort.  The backup
case is generally the worst, but definately not the only case where
this can happen.  It certainly would be non-obvious to the user just
dumping a single set of files (that the system administrator had chosen
to span filesystems) why this failed.

>2) When restoring a mangled name, put it in the right directory under
>the wrong name; then rename will work.
>
>3) If rename fails, attempt a more expensive copy to move the file
>into place.

#2 seems a good solution, but I'd vote for #3.  It's the least impact
change and it does manage the inexpensive rename() in a good 99% of
the cases anyway.  The case of mangled files spanning filesystems
isn't common, it's just really annoying when it does happen.

I'd be happy with #2 as well, if you think extracting the base directory
name isn't too much work.  I think it should be a trivial fix either way.

					Jordan