SysadminNews

KDE Linux: file history with Btrfs and KIO Snapshot

On this page
  1. Three components with different jobs
  2. Recover a file without overwriting the current one
  3. Local history and backup cover different failures
  4. Sources

KDE Linux’s August report describes automatic snapshots of user homes and access through Dolphin. The useful feature is local file history: it can recover an earlier version while the disk works, but does not replace an independent backup.

Btrfs supplies local snapshots, Snapper schedules them, and KIO Snapshot exposes saved versions to Dolphin. A separate backup is needed for loss of the device.
Btrfs supplies local snapshots, Snapper schedules them, and KIO Snapshot exposes saved versions to Dolphin. A separate backup is needed for loss of the device. Chart : PeopleAreGeek. Data source.
View full-size image

Three components with different jobs

KDE’s August 31 report says user homes were converted into Btrfs subvolumes and automatic snapshots enabled. It also reports integration of KIO Snapshot into Dolphin. These are changes to KDE Linux, not a statement that installing Plasma enables this layout on every distribution.

The KIO Snapshot author’s explanation separates creation from browsing. Btrfs supplies snapshots; an orchestrator such as Snapper creates and manages them; KIO Snapshot exposes existing versions to KDE applications through snapshot://. It does not create the history it displays.

Recover a file without overwriting the current one

A useful first exercise is to save a disposable document, wait for a configured snapshot, edit it, and look for the earlier version in Dolphin. Copy that version to a separate filename first. Compare the two before replacing the current document. This tests creation, retention, permissions and browsing together.

If no earlier version appears, check those stages in order. A working file manager cannot retrieve a snapshot that was never taken or has already been removed. Likewise, access restrictions are not proof that the data is absent.

For Snapper-managed snapshots, the author points to ALLOW_USERS and SYNC_ACL=yes for authorized access without running the browser as root. Apply permission changes only to the appropriate account and configuration, rather than granting access across all users’ homes.

Local history and backup cover different failures

EventLocal snapshot can help?
A document overwritten after the snapshotYes, if the version remains accessible
A version older than retention allowsNot if that snapshot has been removed
Lost laptop or failed storage deviceNot from snapshots on that same device

Retained snapshots can also keep old blocks allocated as live files change. Plan retention against real disk usage instead of treating snapshots as free storage. Keep a separate versioned backup and test restoring from it.

The report still described KDE Linux as approaching beta. Try the integrated workflow on a test installation before relying on it for recovery. No filesystem migration is required merely to understand this announcement.

Sources

Checked KDE and the KIO Snapshot author; separated local version history from backup, corrected snapshot permissions and removed broad assumptions about other distributions.