Re: What ostree operations are safe to do concurrently
- From: Alexander Larsson <alexl redhat com>
- To: "Jasper St. Pierre" <jstpierre mecheye net>, Colin Walters <walters verbum org>
- Cc: ostree-list gnome org
- Subject: Re: What ostree operations are safe to do concurrently
- Date: Thu, 10 Dec 2015 11:54:46 +0100
On Thu, 2015-12-03 at 19:12 -0800, Jasper St. Pierre wrote:
Wouldn't a better, lockless solution be to require that the objects
are only moved from tmp/ to the loose-objects/ directory only after
their parent is in the directory?
I don't see how this would help the prune/remove situation?
For instance, if you start a pull operation, and it enumerates all
objects it needs, skipping some that are already installed. But after a
while a prune job starts, which does not see the new ref, so it will
remove objects that are not referenced by others refs. This can end up
removing the objects that the pull assumed was already downloaded.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]