shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

282
active users

#zfs

5 posts5 participants0 posts today
Continued thread

Is there some magical file system/directory structure that will solve my problems? What tools should I be using? I have heard of Johnny Decimal and ZFS and more tools than I care to remember, but I don't know how to start maintaining my own data and infrastructure in a sustainable way!

johnnydecimal.com/

johnnydecimal.comA system to organise your lifeJohnny.Decimal is a system to organise your life. Find things, quickly, with more confidence, and less stress. It's free to use and the concepts are the same at home or work.
#linux#data#backup
Replied in thread

@argv_minus_one @lns hi, one of the rsnapshot devs here - it de-duplicates by hard-linking unchanged files from one backup to the next. Borg is good too though.

But these days my first choice wouldn't be any rsync-a-like, I'd go for #sanoid / #syncoid, which manage #ZFS replication and snapshots. Obviously you still need something rsync-ish to get data onto ZFS if the machine you're backing up can't easily use the One True Filesystem.

sometimes (loud parts of) the #zfs community is an asshole techbro elitist community.

You don't have ECC memory? It's your own fault you have data loss.
You don't run RAID-Z3? It's your own fault you have data loss.
You trusted zfs and don't have backups? It's your own fault you have data loss.
You used SMR drives? It's your own fault you have data loss.
You used consumer SSD? It's your own fault you have data loss.
[…]

Replied in thread

@landley @jschauma @ryanc @0xabad1dea yeah, the exhaustion problem would've been shoved back with a #64bit or sufficiently delayed by a 40bit number.

Unless we also hate #NAT and expect every device to have a unique static #IP (which is a #privacy nightmare at best that "#PrivacyExtensions" barely fixed.)

  • I mean they could've also gone the #DECnet approach and use the #EUI48 / #MAC-Address (or #EUI64) as static addressing system, but that would've made #vendors and not #ISPs the powerful forces of allocation. (Similar to how technically the #ICCID dictates #GSM / #4G / #5G access and not the #IMEI unless places like Australia ban imported devices.

I guess using a #128bit address space was inspired by #ZFS doing the same before, as the folks who designed both wanted to design a solution that clearly will outlive them (way harder than COBOL has outlived Grace Hopper)...

If I was @BNetzA I would've mandated #DualStack and banned #CGNAT (or at least the use of CGNAT in #RFC1918 address spaces) as well as #DualStackLite!

Documentation in operating systems is cool. It is possible to extend and rewrite utilities as time goes on, as #freebsd proves. You can still have cool utilities, like #containers and #zfs and #hypervisors, good docs for them and a consistent base system.

I dunno where I am going with this, other than wishing I didn't have to peruse the Arch wiki and the Gentoo wiki for everything when I get stuck, and instead could just "man xyz" and get good answers, speaking as #nixos user.

Replied in thread
@ianthetechie @feld I can confirm that #Python on #FreeBSD behaves as one would expect. It consumes all RAM (with #ZFS releasing ARC as expected) and then dips into swap. As soon as Python releases memory after the ingestion routine, the swap is purged to near zero and the RAM then becomes available (and used) by the system. Far more predictable and reliable.

If you have big, vertical workloads, FreeBSD is where it is at.

fuckkkk ZFS why you do this. guess i know what i'm spending tonight doing.

any #zfs experts out there able to help me recover my pool? i apparently broke things quite significantly lol