Difference between revisions of "SnapRAID / MergerFS"
From Briki
(→SnapRAID / MergerFS) |
(→Setup) |
||
Line 3: | Line 3: | ||
== Setup == | == Setup == | ||
https://zackreed.me/setting-up-snapraid-on-ubuntu/ | https://zackreed.me/setting-up-snapraid-on-ubuntu/ | ||
− | + | ||
+ | Note that if (like me) you use a dedicated snapraid content directory then you'll need to create that by hand for each disk with: | ||
+ | |||
+ | mkdir /mnt/data/disk1/.snapraid | ||
+ | |||
== Partitioning a new data disk == | == Partitioning a new data disk == | ||
Note: "-m 2" here reserves 2% of the filesystem for root-owned files (eg. .../.snapraid/content) | Note: "-m 2" here reserves 2% of the filesystem for root-owned files (eg. .../.snapraid/content) |
Revision as of 08:43, 10 November 2021
Contents
SnapRAID / MergerFS
Setup
https://zackreed.me/setting-up-snapraid-on-ubuntu/
Note that if (like me) you use a dedicated snapraid content directory then you'll need to create that by hand for each disk with:
mkdir /mnt/data/disk1/.snapraid
Partitioning a new data disk
Note: "-m 2" here reserves 2% of the filesystem for root-owned files (eg. .../.snapraid/content)
sudo parted -a optimal -s /dev/sdX -- mklabel gpt mkpart primary 0% 100% sudo mkfs.ext4 -m 2 -T largefile4 /dev/sdX1
Partitioning a new parity disk
Note: "-m 0" here reserves 0% of the filesystem, ensuring that the parity disks are slightly larger than the data disks
sudo parted -a optimal -s /dev/sdX -- mklabel gpt mkpart primary 0% 100% sudo mkfs.ext4 -m 0 -T largefile4 /dev/sdX1
Adding a new data disk to mergerfs
From: https://zackreed.me/mergerfs-neat-tricks/ From within the root of the mergerfs filesystem (eg. /srv)
xattr -w user.mergerfs.srcmounts '+>/mnt/data/disk4/srv' .mergerfs
Removing a data disk from mergerfs
From within the root of the mergerfs filesystem (eg. /srv)
xattr -w user.mergerfs.srcmounts '-/mnt/data/disk4/srv' .mergerfs
Forcing a resync
sudo snapraid sync