I've posted the question and my own solution to this problem, to make it available to others.
This relates to borg backup and was posted to this borg
github issue: Allow check on read-only filesystems
Trying to access a remote borg repository for list
, info
, mount
and other read-only actions fails when the remote repository resides on a ZFS snapshot (read-only).
I'm backing up using borg with daily pruning (borg prune ...
) for encryption and remote ZFS snapshots for retention (and backup destruction protection).
The crucial reason for doing so, is to protect the backed up data on the remote backup server from an attacker who has access to the host doing the backing up. With read-only ZFS snapshots, the attacker is unable to delete remote backups.
Thus far, I've attempted borg list
, which fails with:
Remote: borg.locking.LockFailed: ('/data/backup/.zfs/snapshot/daily_2017-05-23/home/lock.exclusive', "[Errno 30] Read-only file system: '/data/backup/.zfs/snapshot/daily_2017-05-23/home/lock.exclusive'")