rt/snapraid
1
0
Fork 0
mirror of https://github.com/amadvance/snapraid.git synced 2026-10-26 02:49:02 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update manpage

Browse source
This commit is contained in:
Andrea Mazzoleni 2026-04-29 12:18:23 +02:00
parent fb051e02c7
commit 8a727975ab
4 changed files with 167 additions and 70 deletions
Download patch file Download diff file Expand all files Collapse all files

15
snapraid.conf.example
View file

@ -50,18 +50,25 @@ extra boot /
# start of a 'sync'. This ensures a consistent, point-in-time view of your
# files, preventing errors caused by concurrent file modifications.
#
# This option applies exclusively to data disks formatted with the Btrfs
# filesystem. Parity disks, or data disks using other filesystems, will
# always use the live version of the filesystem.
#
# This significantly improves recovery: if a file is deleted from the live
# filesystem, it remains preserved in the snapshot. This prevents the parity
# from becoming "broken" for that block, ensuring you can still successfully
# recover data if another disk fails.
#
# Only Btrfs is supported. Snapshots are stored in a hidden '.snapraid'
# directory at the root of each data subvolume.
# directory at the root of the Btrfs subvolume containing your data.
# SnapRAID will automatically detect the subvolume root for each data path.
#
# Two snapshots are managed per disk:
# .snapraid/pending - The snapshot currently being processed.
# .snapraid/stable - The last successfully completed sync state.
# Snapshot creation and deletion require administrative privileges.
# Ensure SnapRAID is run with the necessary permissions (e.g., sudo) when
# this option is enabled.
#
# See the 'Snapshots' section in the snapraid(1) manpage for a detailed
# explanation of the snapshot lifecycle.
#snapshot
# Excludes hidden files and directories (uncomment to enable).