Storage & backup
Map disks and mounts, understand filesystems, and plan a verifiable restore.
Identify the device, filesystem, mount, and backup destination before acting. A mounted disk is not a backup; a completed backup still needs a restore check. Keep diagnostic reads separate from formatting, repair, and deletion.
Begin with lsblk and findmnt to map the system. Read filesystem-specific guidance before repairs. Use restic or Borg's restoration documentation to test recovering representative files to a separate directory.
No matching references. Try a broader term or clear the filters.
Map disks and mounts, understand filesystems, and plan a verifiable restore.
-
lsblk: map block devices
Inspect the relationship between disks, partitions, and filesystems; select output columns explicitly for scripts.
Linux util-linux · Project documentation · Selection reviewed -
findmnt: inspect mounted filesystems
Identify the source, target, and options of a mount when an application is writing to an unexpected filesystem.
Linux util-linux · Project documentation · Selection reviewed -
Btrfs administration documentation
Look up subvolume, snapshot, scrub, and recovery concepts before choosing a Btrfs maintenance operation.
Upstream latest · btrfs-progs · Project documentation · Selection reviewed -
ext4 administration guide
Understand ext4 mount options and implementation details; compare kernel version before applying a setting.
Current upstream kernel documentation · Project documentation · Selection reviewed -
Restore files with restic
Recover a snapshot into a separate destination and explore backed-up files when rehearsing a restore.
restic · stable documentation · Project documentation · Selection reviewed -
Borg backup quick start
Follow the repository, archive, inspection, and extraction workflow before designing a recurring backup routine.
Borg · stable documentation · Project documentation · Selection reviewed
How this library is selected
References are selected for a concrete operational task, with preference for project and distribution documentation. Annotations describe when to use a source; version labels make its scope explicit.
Selection reviewed means the destination, subject, and version scope were checked. It is not a claim that every upstream command has been tested. Original guides identify their own test environment. Platform filters also include references that apply across distributions.