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

Add Bcachefs support

Browse source
This commit is contained in:
Andrea Mazzoleni 2026-05-03 21:39:35 +02:00
parent 4a37e3fece
commit 16b08201a4
15 changed files with 387 additions and 129 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/snapraid.1
View file

@ -1434,18 +1434,18 @@ When enabled, SnapRAID creates a read\-only snapshot of your data at the
start of a \'sync\'. This ensures a consistent, point\-in\-time view of your
files, preventing errors caused by concurrent file modifications.
.PP
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 option applies exclusively to data disks formatted with the
Btrfs or Bcachefs filesystems. Parity disks, or data disks using
other filesystems, will always use the live version of the filesystem.
.PP
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 \[dq]broken\[dq] for that block, ensuring you can still successfully
recover data if another disk fails.
.PP
Only Btrfs is supported. Snapshots are stored in a hidden \'.snapraid\'
directory at the root of the Btrfs subvolume containing your data.
SnapRAID will automatically detect the subvolume root for each data path.
Snapshots are stored in a hidden \'.snapraid\' directory at the root
of the subvolume containing your data. SnapRAID will automatically
detect the subvolume root for each data path.
.PP
Snapshot creation and deletion require administrative privileges.
Ensure SnapRAID is run with the necessary permissions (e.g., sudo) when
@ -1833,7 +1833,9 @@ fix other failed disks.
.PP
Snapshots are created only for data disks and only if the underlying
filesystem supports this functionality. Parity disks always use
the live filesystem. At present, this is supported exclusively on Btrfs.
the live filesystem.
.PP
At present, this is supported exclusively on Btrfs and Bcachefs.
.PP
You can mix data disks with different filesystems. Only those that
support snapshots will utilize them, while other disks will continue

16
doc/snapraid.d
View file

@ -1154,18 +1154,18 @@ Configuration
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 option applies exclusively to data disks formatted with the
Btrfs or Bcachefs filesystems. 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 the Btrfs subvolume containing your data.
SnapRAID will automatically detect the subvolume root for each data path.
Snapshots are stored in a hidden '.snapraid' directory at the root
of the subvolume containing your data. SnapRAID will automatically
detect the subvolume root for each data path.
Snapshot creation and deletion require administrative privileges.
Ensure SnapRAID is run with the necessary permissions (e.g., sudo) when
@ -1445,7 +1445,9 @@ Snapshots
Snapshots are created only for data disks and only if the underlying
filesystem supports this functionality. Parity disks always use
the live filesystem. At present, this is supported exclusively on Btrfs.
the live filesystem.
At present, this is supported exclusively on Btrfs and Bcachefs.
You can mix data disks with different filesystems. Only those that
support snapshots will utilize them, while other disks will continue

16
doc/snapraid.txt
View file

@ -1232,18 +1232,18 @@ When enabled, SnapRAID creates a read-only snapshot of your data at the
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 option applies exclusively to data disks formatted with the
Btrfs or Bcachefs filesystems. 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 the Btrfs subvolume containing your data.
SnapRAID will automatically detect the subvolume root for each data path.
Snapshots are stored in a hidden '.snapraid' directory at the root
of the subvolume containing your data. SnapRAID will automatically
detect the subvolume root for each data path.
Snapshot creation and deletion require administrative privileges.
Ensure SnapRAID is run with the necessary permissions (e.g., sudo) when
@ -1550,7 +1550,9 @@ Recovery - If a file is updated or deleted from the live filesystem,
Snapshots are created only for data disks and only if the underlying
filesystem supports this functionality. Parity disks always use
the live filesystem. At present, this is supported exclusively on Btrfs.
the live filesystem.
At present, this is supported exclusively on Btrfs and Bcachefs.
You can mix data disks with different filesystems. Only those that
support snapshots will utilize them, while other disks will continue