Re: how to deal with ostree corruption

On Fri, Feb 2, 2018, at 6:55 AM, Dan Nicholson wrote:

Since the checkout is a hardlink to the repo object, the test you
showed below would not allow you to simply checkout the uncorrupted
object again. That's how "ostree fsck" knows there's a problem. :)

What you'd have to do is remove the object, pull it from the remote
again and check it out again. There's nothing (to my knowledge) in
ostree for managing this process since it pretty much requires manual

and specifically

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