Re: Making ostree robust wrt concurrent use

On fre, 2015-12-11 at 11:23 +0100, Alexander Larsson wrote:
3) During the operation we naturally build up a topological sorting
   all the objects involved in the operation. For instance, during a
   pull we do a recursive discovery of all objects that are not
   available in the local repo. We save this order, and then use the
   reverse order when moving non-leaf (DIR_META & COMMIT) objects
   the repo, doing an fsync of the object directories whenever we
   all children of some object have been moved.

Actually, this doesn't work because if static deltas are in use we just
always trust that they have all the objects (or they are listed as
fallbacks), so we never build up the topological sort. I guess we need
to manually do this at the end of the transaction.

 Alexander Larsson                                            Red Hat, Inc 
       alexl redhat com            alexander larsson gmail com 
He's a genetically engineered playboy barbarian on the edge. She's a 
disco-crazy Bolivian journalist prone to fits of savage, blood-crazed 
rage. They fight crime! 

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]