Re: how to deal with ostree corruption

[Dusty Mabe <dusty dustymabe com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 02/02/2018 06:55 AM, Dan Nicholson wrote:
> On Thu, Feb 1, 2018 at 5:26 PM, Davis Roman <davis roman84 gmail com> wrote:
> > Hello,
> >
> > I'm trying to learn how ostree deals with file corruption so I set up
> > scenario where a library in /usr/lib is modified/corrupted and now ostree
> > fsck is reporting a corrupted object.
> >
> > I'd like to know if it's possible to checkout the original version from the
> > ostree repo and wipe any corrupted/modified files that are currently live.
>
> 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
> intervention.

Should be pretty easy to automate, though, right? Maybe we should file an RFE?
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlp0YD8ACgkQMwLb1zlS
5nEWNxAA0N+apvZ6cHla5hzOJG2eDYxs1465vuPskdyrbmfMtVmwteuSKwA/gC++
m7WE7OMcKbAex5jlRphAZWuZWLo1MWrOKln9wavMT22wEea1/rr6EiPLG5NtT4I8
lSlmsTRNAZtbkukBEjHJYTMltTGiQx6kTiuHS05QwZSYmAE8heUlR6mQShBH968M
fjbGgBK48NCE6Gf7l9BrUBLmMuu9nGpn0RIpAnzZ8iv5GSvWjJiUn1YJD9+bEpq2
x6W5A2oiSZuPsut5WZfTzhyND2p22YJCsWvK7kzBRqXWLrWTloYFp+0OtMEy0Qpd
4A1vx6Vc4XlTpwESh+wrTJRtQm2HT/mkHLi9ThB4RXicBooCrHHAMTQsyYqIniNY
Mis/IRvaxMItnlLgUEVnxzWxgcEy6P4qepAVf+XSTM/StVvyMFTQ/34gtV8Yvb+r
epnWOliwA7rRy3tTCaXDKjU9DbCza9yzbqMIMRefuoCEfxTfCOH5OFQbyZfNfC+P
DatiorvqnhqPmG6y+aUSCabk3F6vNfQEOmKsLWihtPweIngknR+f3j6xSAn0kbkG
O39HwAcsxVZuI2Wd+1h/NsAnTQYQCzBSVOmzy78vGtbxAbFTvXMV1wn2H72MXP0k
aPAFoX4otFLP+ufsaV0yFxnjjGtWGBNFzNnG9O+PAJ0xco8YgGw=
=D5Er
-----END PGP SIGNATURE-----