14.2 A Failed Rollback
The rollback itself fails: a write error, a filesystem gone read-only, a permission change mid-operation.
14.2.1 What is left #
Some originals restored, some still at their backup paths. Some new files removed, some still at their final paths. The database holding the pre-transaction state, because the commit never ran.
14.2.2 What peipkg does #
Discards the error, closes the journal's transaction as rolled back, and returns.
14.2.3 What that means for the next operation #
Recovery looks for a pending transaction and finds none, so it does not retry. The history shows an authoritative-looking rolled-back record. Nothing tells the operator the rollback did not complete.
14.2.4 The signal that is available #
peipkg verify re-hashes every recorded file against what is on disk.
Files the rollback failed to restore will not match their recorded
hashes, and will be reported as modified.
A directory listing around the affected paths shows the leftovers directly: siblings carrying the backup and staged markers with the failed transaction's identifier.
14.2.5 Getting back to a known state #
Identify the affected paths, decide whether the old or the new content is wanted, remove the leftover siblings, and reinstall the affected packages so that the database and the filesystem agree again.