On Sat, Jan 06, 2007 at 07:14:38PM -0500, Catalin Patulea wrote:
> On Sat, 6 Jan 2007, Josef Sipek wrote:
> ...
> >Unionfs retries operations only when going from lower priority branch to
> >one of higher. The case you describe, is the opposite - going from higher
> >priority branch to lower. In the case of mknod, what would happen if mknod
> >failed because a file already exists under that name? If unionfs tried to
> >create the node on a lower priority branch, the new node file would be
> >hidden by the one in the higher priority branch => very bad.
> Hmm. I had to sit and think about it for a while, but I think I
> understand.
>
> Can you give an example of a low-to-high operation that unionfs supports
> that it would retry?
Writing to a file. If the write fails (eg. read only filesystem), unionfs
copies the file up to a higher priority branch, and then retries
> And my problem still stands.. the vfat+tmpfs idea. Care to offer any
> ideas/advice on that topic?
How frequently do you wish to create device nodes and other special files?
If not very frequently, could you just try to create all of the files you
need before you mount the union?
You could of course try to create the node files on the lower filesystem
and then run uniondbg -g to increment the generation count of the union.
(Generally considered bad, but some people use it.)
Josef "Jeff" Sipek.
--
Research, n.:
Consider Columbus:
He didn't know where he was going.
When he got there he didn't know where he was.
When he got back he didn't know where he had been.
And he did it all on someone else's money.
_______________________________________________
unionfs mailing list
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
