fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

#ZFS

27 posts25 participants2 posts today

🔁 RAID vs ZFS

RAID: tecnología que agrupa discos para mejorar rendimiento o seguridad según el nivel que elijas (RAID 0, 1, etc.). Es simple, útil y eficiente para muchas tareas.

ZFS : sistema de archivos + gestor de volúmenes que incluye su propio tipo de RAID, snapshots, compresión, verificación de integridad...

¿Lo básico? RAID.
¿Potencia y control? ZFS es el camino.

🔗 Descubre más en nuestra sección de tutoriales en la web:

slimbook.com/blog/tutoriales-2

#RAID#ZFS#TechTips
Replied in thread

@vermaden @justine
Addendum: prefix "pkg upgrade" with "make-snapshots" to be able to rollback the file systems(s) without fuss ...

make-snapshots \
&& pkg upgrade && make-snapshots \
&& pkg autoremove && make-snapshots \
&& pkg clean && make-snapshots

... I had made the change before the issue of {missing,disappearing}-packages-on-upgrade that various other peoples are experiencing currently.

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.

Meanwhile on the NAS;

zpool replace tank sdb /dev/sdc

My fancy new Toshiba MG09 HDDs arrived today (18TB MG09ACA18TE).

The 1st MG09 is currently running in a USB "toaster". Once "zpool replace" finishes, i'll shut the box down and physically replace the 10TB HDDs with the new ones. One of the 10TB HDDs will then go in the toaster, and i'll "zpool replace" it with the now internal remaining MG09.

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

Today, out of nowhere, my shell started to misbehave. My prompt suddenly reverted to default. Some unexpected "command not found" errors started popping up. Something was off.

I went to check my shell configuration. The directory was not there. I then went look into ~/.config. Half of the directories inside were simply gone.

I immediately flipped into what the fuck is happening mode.

This system is an Alpine root-on-ZFS. I have a script called by cron every 20 minutes that snapshots everything.

First I went into the snapshot directory and started copying some things. I soon noticed it was just too much missing. How to map out what was gone in the first place? Even so, copying would only go so far because I was duplicating things.

I looked to my left at the resource monitor. I had less than 1 GB left of free space. That was not going to work.

I flip some pages, looking for an incantation...

% zfs rollback zroot/home@20m

A long second hanged in the air. Then all the resource monitor's bars flipped at once to green: 53% free space.

"Blessed be the ZFS Daemons and the Authors who conjured Them."

The system was still confused, so I rebooted. It let its conscience drift - as it is used to -, uncertainty still heavy in the air. Then it resurfaced... every line of output unconcerned.

Back up, no trace was left of the seconds leading up to the warp. The only suspicion came from a cryptography guardian, who noticed something was wrong about the timestamps. "Please re-enter the passcodes", it asked. Every other blob was either unconcerned or unimpressed with the glitch.

Like any time travel, the only trace left was in my memory. No history anywhere has me looking for that spell. I booted 20 minutes into the past and that's from when I am writing to you.

A nice side effect of expanding my ZFS pool is that scrubs are now quite a bit faster. Down from ~19 hours to under 15. Makes sense since it can read data faster now.

I'd still like to know why the speed of scrubs decreases over as it progresses.

scrub repaired 0B in 14:27:28 with 0 errors on Mon Apr 14 14:51:33 2025

Still messing around with my system with broken FS. To be honest, has never been so problematic to me in the past. But I have to admit that I never used raid5 there (known to be broken), while I do use raidz on .