Charles P Wright: > > - then, i am afraid the stacked_fs cannot follow the i_stacked_inode > > chain. read from /stacked_fs/fileB. you will see the old contents of > > fileA, won't you? > That seems right. I don't think any current Unionfs solution fixes that, > but this issue is orthogonal to the i_stacked_inode solution, which means > that Unionfs at least knows two lower-level files are the same when it > instantiates Unionfs inodes.
I am afraid you are forgetting the persistent inumber again. As you know, it is not perfect. But it has a chance to be the solution. If you access fileA before fileB, you will see the correct filedata. With i_stacked_inode, you will not, won't you? Junjiro Okajima _______________________________________________ unionfs mailing list [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
