Shaya Potter: > if you create a new directory, such that it's opaque, you can't then in > the future delete it, as the directory isn't empty and the opaque file > isn't deleted. > > I think readdir_util_callback() might be getting confused > by .wh.__dir_opaque.
I think it is a problem of unionfs_permission(). When the target dir is on both rw and ro branches, it checks the dir on rw first, then on ro. Second time it gets EPERM and returns. I saw it under the environemnt of unionfs-20040929-0844/linux-2.6.13.2/iso9660/tmpfs. When the target is a file, unionfs_permission() returns after checking rw branch. I dont know why unionfs_permission() needs to check the second hidden entry. Junjiro Okajima _______________________________________________ unionfs mailing list [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
