Skip to content
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.

repair: Rework to be more introspectable #505

Merged
merged 1 commit into from
Jul 21, 2023

Conversation

cgwalters
Copy link
Member

I plan to "productize" this repair code a bit more in OpenShift at least, and I think other admins may want to do similar outside of that too.

In order to make that more reliable:

  • Better split the "fsck/--dry-run" path from "repair" i.e mutation
  • Introduce a --write-result-to argument that outputs JSON. This allows us to better distinguish the tristate of "OK" from "corruption detected" to "tool failed for some other reason"

Further:

  • Drop the check for derived commits, let's just always check the inodes because it's not very expensive in the end and it's just really useful to do.
  • Add checks for whether the booted deployment is potentially affected, as this is important information; we'll need to redeploy and reboot if so

I plan to "productize" this repair code a bit more in OpenShift at
least, and I think other admins may want to do similar outside
of that too.

In order to make that more reliable:

- Better split the "fsck/--dry-run" path from "repair" i.e mutation
- Introduce a `--write-result-to` argument that outputs
  JSON.  This allows us to better distinguish the tristate of
  "OK" from "corruption detected" to "tool failed for some other reason"

Further:

- Drop the check for derived commits, let's just *always* check
  the inodes because it's not very expensive in the end and
  it's just really useful to do.
- Add checks for whether the booted deployment is potentially
  affected, as this is important information; we'll need to redeploy
  and reboot if so
Copy link
Member

@jmarrero jmarrero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jmarrero jmarrero merged commit f0f1b16 into ostreedev:main Jul 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants