Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up fsck errors #2522

Closed
buggtb opened this issue Jan 20, 2022 · 2 comments
Closed

Clean up fsck errors #2522

buggtb opened this issue Jan 20, 2022 · 2 comments

Comments

@buggtb
Copy link

buggtb commented Jan 20, 2022

I've been trying to clean up a broken Fedora install.

ostree fsck complained about various corrupt files, so using a combination of stuff from the internet I figured that:

#345 (comment)

This comment helped somewhat and also:

https://bugzilla.redhat.com/show_bug.cgi?id=1333010

Messing with the refs and pulling a fresh instance got rid of most but I'm still let with:

💀39% ✗ sudo ostree fsck 
Validating refs...
Validating refs in collections...
Enumerating objects...
Verifying content integrity of 68 commit objects...
fsck objects (132256/132256) [=============] 100%
1 partial commits not verified
error: 1 partial commits from fsck-detected corruption

And I can't figure out how to remove the last error for a clean tree.

@buggtb
Copy link
Author

buggtb commented Jan 20, 2022

Alright, dunno what I'm doing but I ran:

rpm-ostree rebase fedora:fedora/35/x86_64/silverblue

and it went away :)

@buggtb buggtb closed this as completed Jan 20, 2022
@dbnicholson
Copy link
Member

It's unfortunate that fsck doesn't tell you which commit is partial. OSTree also doesn't have a built-in way to describe a commit in terms of refs. But ultimately the way to fix a partial commit is to pull it. I suppose rpm-ostree either did that or the new commit caused the partial commit to be pruned since it was no longer a ref head.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants