Site Tools


start:isbtrfsok

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
start:isbtrfsok [2022/11/04 19:24] peterstart:isbtrfsok [2024/01/24 19:49] (current) peter
Line 1: Line 1:
 +DATE CHECKED THIS PAGE WAS VALID: 14/09/2023 
 +
 BTRFS is working well at the moment on a single disk, or with RAID1C3 (metadata also RAID1C3 as 2 disks can fail) in a NAS environment with more than 3 disks (ie 4+ disks). For 2 or 3 disks RAID1 is preferred which also works well (data is duplicated so it can still self heal and 1 disk can fail). Note: For RAID 6 to avoid loss of data/corruption on a power failure/kernel hang you must raid the metadata differently although RAID6 still has some potential issues so its not advised to use it. Its mostly ready but has a few edge cases where data can be lost they are fixing still. eg: imagine 6 disks the command to create the RAID6 array is: BTRFS is working well at the moment on a single disk, or with RAID1C3 (metadata also RAID1C3 as 2 disks can fail) in a NAS environment with more than 3 disks (ie 4+ disks). For 2 or 3 disks RAID1 is preferred which also works well (data is duplicated so it can still self heal and 1 disk can fail). Note: For RAID 6 to avoid loss of data/corruption on a power failure/kernel hang you must raid the metadata differently although RAID6 still has some potential issues so its not advised to use it. Its mostly ready but has a few edge cases where data can be lost they are fixing still. eg: imagine 6 disks the command to create the RAID6 array is:
  
Line 21: Line 23:
 A weekly scrub AND balance is suggested in a RAID environment so that self healing and filesystem maintenance is performed. For a single disk just a monthly scrub is fine and you can run it manually or schedule one with cron if you prefer. If there are any corrupt files, it cant self heal anyway so you would be restoring from backup, and balancing on a single disk generally happens automatically to a degree so I normally dont worry about it (only 1 copy of data is kept). A weekly scrub AND balance is suggested in a RAID environment so that self healing and filesystem maintenance is performed. For a single disk just a monthly scrub is fine and you can run it manually or schedule one with cron if you prefer. If there are any corrupt files, it cant self heal anyway so you would be restoring from backup, and balancing on a single disk generally happens automatically to a degree so I normally dont worry about it (only 1 copy of data is kept).
  
-For single disks in a home PC I use the following mount options in FStab: defaults,compress=lzo,autodefrag,discard=async,space_cache=v2+For single disks in a home PC I use the following mount options in FStab: defaults,compress=lzo,discard=async,space_cache=v2
  
-So for example a disk would be mounted as such in the fstab: UUID=383732b1-5e87-4b68-a15a-f044bc559877 / btrfs defaults,compress=lzo,autodefrag,discard=async,space_cache=v2,subvol=@ 0 0+So for example a disk would be mounted as such in the fstab: UUID=383732b1-5e87-4b68-a15a-f044bc559877 / btrfs defaults,compress=lzo,discard=async,space_cache=v2,subvol=@ 0 0
  
 This keeps things nice and tidy and automatically handles trim, and balance. As mentioned there is no self healing on a single disk so you can run a scrub to check for errors every now and again but a backup is needed to restore files. Dont forget to dup metadata even on a single disk. That is in this wiki elsewhere if you dont know how.  This keeps things nice and tidy and automatically handles trim, and balance. As mentioned there is no self healing on a single disk so you can run a scrub to check for errors every now and again but a backup is needed to restore files. Dont forget to dup metadata even on a single disk. That is in this wiki elsewhere if you dont know how. 
  
 Overall BTRFS is production ready now since Linux Kernel 6 onwards. There are a few gotchas but nothing major and if you use RAID1C3/4 data is kept safe.  Overall BTRFS is production ready now since Linux Kernel 6 onwards. There are a few gotchas but nothing major and if you use RAID1C3/4 data is kept safe. 
 +
 +Also note: autodefrag is no longer needed or reccomended on SSD disks. Do not use this mount option.
start/isbtrfsok.1667589899.txt.gz · Last modified: 2022/11/04 19:24 by peter