Open karuboniru opened 5 months ago
I somehow break the system status again without doing anything related to package layering, so the issue is not limited to the layering...
And the file being broken is
ostree ls 44eb1b1af8bad1129fbe70ccf0b092d54514867d01d4b17b4d5d27808113befb -CR|grep 944eec75e5b011eabe3643394c7bab36b5cb531d1e4ccab905a9e49f3ffcb70e
-00644 0 0 32768 944eec75e5b011eabe3643394c7bab36b5cb531d1e4ccab905a9e49f3ffcb70e /usr/share/rpm/rpmdb.sqlite-shm
This might be an rpm-ostree bug. Could you report that upstream? Thanks
Describe the bug Start with a system with some overrrides:
Rebase to a container image, with simliar package list
Ends up with broken commit,
ostree fsck
complains about broken files. Andbtrfs scrub
don't report any corrupted file.To Reproduce Please describe the steps needed to reproduce the bug:
Expected behavior I think the rebase is quite straightford, and should not lead to any corrupted ostree commit
Screenshots If applicable, add screenshots to help explain your problem.
OS version:
Additional context Tried rebasing from clean installation and gets clean fsck. So the layering has something to do with this. And doing
rpm-ostree reset
before rebasing also did the trick. (So resetting before rebasing is the workaround)If rebasing from dirty image is not supported I believe a warning before the actual execution is needed to avoid confusion.
The
Containerfile
is https://github.com/karuboniru/ostree-container