nixCraft, to linux
@nixCraft@mastodon.social avatar

#Linux filesystem comparison

kkarhan,

@ernstdemoor @nixCraft that's because on basically all #Linux #Filesystems, #RAID and #Encryption is handled by dedicaded subsystems like #dmraid and #dmcrypt / #LUKS respectably, thus not on filesystem but OS level...

This allows extra cursed shit like a an encrypted & RAID-5 running NTFS - Tho that won't be useable by anything but Linix and I disrecommend it almost as hard as mixing hardware RAID controllers and/or dmraid with ZFS.

Remember: NEVER EVER LIE TO ZFS!!!

kkarhan,

@brli @nixCraft not in every case.

i.e. #btrfs and #ZFS have their own #VolumeManager|s integrated and thus don't like being lied to aka. #dmraid and/or #dmcrypt and/or Hardware-#RAID - Controllers...

https://pleroma.breizh.pm/objects/8108545b-3b05-438e-bf2a-a584a90c1298

scy, to debian
@scy@chaos.social avatar

Turns out, #LVM #RAID-1 with #dmintegrity over two separate physical disks and then putting a #dmcrypt device on top of the RAID is really slow. As in, it's estimating to take a week to do the initial sync on the two 12TB WD Red drives on SATA. (For comparison, zeroing out one of these disks should take 8 hours or something.)

Apparently it's a somewhat-known problem with dm-integrity, related to its journal.

How would you build something bitrot-safe & encrypted with that hardware? #Debian 12.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • mdbf
  • everett
  • osvaldo12
  • magazineikmin
  • thenastyranch
  • rosin
  • normalnudes
  • Youngstown
  • Durango
  • slotface
  • ngwrru68w68
  • kavyap
  • DreamBathrooms
  • tester
  • InstantRegret
  • ethstaker
  • GTA5RPClips
  • tacticalgear
  • Leos
  • anitta
  • modclub
  • khanakhh
  • cubers
  • cisconetworking
  • provamag3
  • megavids
  • lostlight
  • All magazines