Paul, I've verified that the bug doesn't exist in Unionfs-2.1. As Jeff hinted, you're probably using Unionfs 1.x, right? If so, we strongly recommend you upgrade to 2.1 -- this and many bugs are fixed. Cheers, Erez.