• 7 Posts
  • 133 Comments
Joined 2 years ago
cake
Cake day: June 17th, 2023

help-circle

  • It’s hard to tell sometimes. Especially when it’s such a sensitive issue where normies will parrot the same ignorant crap over and over again. I one went off on someone, not even considering it was in-jest, because is was so convincingly written.

    The /s is important people. I know it slightly reduces the impact of the joke but some people believe that shit 110%.



  • Not really. Even TrueNAS Core (ZFS) highly recommends ECC memory to mitigate this possibility from occurring. After reading more about filesystems in general and when money allowed, I took this advice as gospel when upgrading my server from junk I found laying around to a proper Supermicro ATX server mobo.

    The difference I think is that BRTFS is more vulnerable to becoming unmountable whereas other filesystems have a better chance of still being mountable but contain missing or corrupted data. The latter usually being preferable.

    For desktop use some people don’t recommend ZFS as if the right memory corruption conditions are met, it can eat your data as well. It’s why Linus Torvalds goes on a rant every now and then about how bullshit it is that Intel normalized paywalling ECC memory to servers only.

    I disagree and think the benefits of ZFS on a desktop without ECC outweigh a rare possibility that can be mitigated with backups.






  • Fuck Electron. I hate that current trend. I like my long battery life and being able to run more than 3 applications on my MacBook Pro.

    I will always use the example of how I subscribed to Spotify for a couple months back in 2015 and realized that the app constantly sat at the top of the Using Significant Energy list on my mac and was the reason the fan was so loud. I switched away to Apple Music for that sole reason. iTunes by comparison was very power efficient. It plays music for gods sake. How can you fail at playing music that badly.











  • My solution is RAIDZ5 and storing the backup on LTO6 tape with parity/erasure code. I think the fact that scrub times take 24 hours even on 16TB drives is already over the safety margin. If a drive failure happens, the first thing I’ll do to run a manual diff backup which should take a fraction of the time and then run the ZFS resilver.

    I’m beginning to see why SSD RAID is being considered now. My guess for HDDs in enterprise is that a RAID 15 (I made this up) would be considered. What I mean is data is stored on two identical servers each running RAID5 or 6. Off the shelf solutions like Gluster exist and that seems to be gaining traction at least according to Linus Tech Tips.