one thing to note about this patch. Without it, branching/heavy use seem to deadlock the machine.
With it, it runs much longer (many times completing the postmark), but I'm able to get a repeated "Unable to handle kernel paging request" in the branchman code, which from my previous message seems to indicate that unionfs is corrupting some of its internal data structures somehow. On Thu, 2006-01-19 at 14:05 -0500, Shaya Potter wrote: > this patch changes the use of the read/write lock to force serialization > on the branch table. > > basically, any entry point that can change it (ioctl for adding/changing > mode/inc) is taken with write, while every other fs entry point (lookup, > read, write....) is taken with read. basically to force the fs not to > be in use when a branching operation is taking place. > > thoughts? > > it also does one other thing, makes all (I believe) the > branchget/branchputs follow this model. > > 1. branchget before open(). > > 2. branchput after fput(). > _______________________________________________ > unionfs mailing list > [email protected] > http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs _______________________________________________ unionfs mailing list [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
