Btrfs Root Snapshot Rollback and RPM Database Synchronization

Direct answer

No. A Btrfs root snapshot rollback reverts the RPM database together with the rest of the root subvolume, but it does not synchronize that database with external volumes or separate partitions. DNF likewise cannot coordinate package changes with data-schema changes outside the root filesystem.

Likely explanation

A snapshot rollback restores the selected root subvolume to an earlier point in time. Because /var/lib/rpm lives on that subvolume, the RPM database returns to the package set recorded when the snapshot was created. Data stored on a separate mount—such as an application database on its own partition—is outside the subvolume and keeps its post-snapshot state. The result is a reverted package inventory paired with newer external data, which can fail if the application expects the schema that accompanied the rolled-back package versions.

Confirmed behavior

• Btrfs rollback covers only the rolled-back root subvolume; external mounts are untouched.
• The RPM database and root binaries revert together within that subvolume.
• DNF transactions do not coordinate with external filesystems or application schema migrations.
• No built-in Btrfs or DNF feature automatically realigns the RPM database with external volume state after rollback.

Steps for this case

1. Determine whether the external data is inside or outside the root subvolume:

findmnt -T /path/to/external/data
btrfs subvolume list /

2. Verify the reverted package state:

rpm -qa

3. Reconcile manually. Run the application's pending schema migration, restore the external data from a backup taken before the update, or reinstall packages removed by the rollback until package versions and data schema match.
4. To prevent recurrence, keep tightly coupled application data inside the root Btrfs subvolume, or treat schema changes as independent operations that must be reversed or reapplied separately after any rollback.

Diagnostic detail needed

Is the external data stored on a separate partition or mount point outside the Btrfs root subvolume? If it resides inside the subvolume, the rollback reverts it along with the RPM database; if it is separate, manual reconciliation is the only supported path.

Assumption: this describes Fedora systems booting Btrfs root subvolume snapshots through GRUB. The filesystem boundary rule is consistent across Btrfs implementations, though snapshot tooling such as snapper may change how entries appear in the boot menu.