Difference between revisions of "SnapRAID / MergerFS"

From Briki
Jump to: navigation, search
(Partitioning a new data disk)
Line 5: Line 5:
 
    
 
    
 
== 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)
 
   sudo parted -a optimal -s /dev/sdX -- mklabel gpt mkpart primary 0% 100%
 
   sudo parted -a optimal -s /dev/sdX -- mklabel gpt mkpart primary 0% 100%
 
   sudo mkfs.ext4 -m 2 -T largefile4 /dev/sdX1
 
   sudo mkfs.ext4 -m 2 -T largefile4 /dev/sdX1
 +
 +
== Partitioning a new parity disk ==
 +
Note: "-m 2" 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
  
 
== Forcing a resync ==
 
== Forcing a resync ==
  
 
   sudo snapraid sync
 
   sudo snapraid sync

Revision as of 16:54, 13 January 2021

SnapRAID / MergerFS

Setup

https://zackreed.me/setting-up-snapraid-on-ubuntu/

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 2" 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

Forcing a resync

 sudo snapraid sync