As you might imagine, I was really happy to see this issue get some attention recently and I don't want to sound ungrateful, but this fix doesn't actually help us or the majority of 'Enterprise' users since many are likely still using Unix and Java 6 and will be for several years to come.

How about adding a configurable attribute on the policy that would default to the current behavior (which I agree is safer/better in the Java 7 world), but allow users to force the rename-by-copy for any failure (or even just force it to always use rename-by-copy without even trying the default method)?