Mastodawn

🇬🇧 Ever wondered how burningboard.net actually runs?

Fully self-hosted in Germany, no trackers, no external logging. Isolated FreeBSD jails, a strict firewall, ZFS and encrypted off-site backups (restore-tested twice a year). Sovereign and transparent. All the details: https://meta.burningboard.net/infrastruktur.html

🇩🇪 Wie läuft burningboard.net eigentlich?

Komplett selbst gehostet, in Deutschland, ohne Tracker und ohne externes Logging. Isolierte FreeBSD-Jails, strikte Firewall, ZFS und verschlüsselte Offsite-Backups (2x im Jahr per Restore getestet). Souverän und transparent. Alle Details: https://meta.burningboard.net/infrastruktur.html

#mastoadmin #freebsd #zfs #gdpr #digitalsovereignty #fediverse

Unsere Infrastruktur - burningboard.net

Wie wir burningboard.net betreiben: souverän, sicher und vollständig in eigener Hand. Segmentierte FreeBSD-Architektur, verschlüsselte Offsite-Backups und Hosting in Deutschland.

burningboard.net

da_am

17h ago

Going to try out zfs.rent. You send them a hard drive or mirror pair and they put it in a machine in a data center. Cool way to zfs send snapshots and seems fairly inexpensive. Anyone using them?
#zfs

anparker 1d ago

(I'm experimenting with Docker Engine 29.0+ here and, maybe, I'm reinventing the wheel, but...)

I do like #FreeBSD and I like #ZFS. So, I thought, I can use OpenZFS on linux too... With docker... Right... Well....

ZFS storage driver is apparently slow as hell and overlay2 don't really work on ZFS.
So, the best option I found, just create a zvolume, format it with something linux friendly and go with it.
But that's kinda killing entire idea of having pools of storage you can mess however you need.

But hey, docker only need overlay for root on it's containers. I can keep everything else on zfs.
And that where it's became interesting (rabbit hole)...

Nothing goes to rootfs... MM, why? o_O

https://gist.github.com/anparker/c4c7a6c2f96a253ba6f4fed344d9037c

zfs_test.txt

GitHub Gist: instantly share code, notes, and snippets.

Gist

Spitfire 1d ago

ZFS is so goddamn cool 😻

#linux #zfs

Multi Purr Puss

2d ago

Something must've gone wrong; i reckon, it's fixed, now? Publishing another release, within a few days, feels like "a good sign"?

I'm talking about #NextCloud.
I'm also talking about VMs and #ZFS snapshots.

I'm so glad, that i'm using #ZEDfs snapshots - the type of snapshots, with the correct pronunciation. -.-

#Linux #HomeLab

furicle 2d ago

Hmmmm - swapped some systems to #zfs 2.4 yesterday, and today zabbix is showing low ram alerts.

Looking closer, yep, ARC is using almost all of it. Which I should have expected.
https://blog.thalheim.io/2025/10/17/zfs-ate-my-ram-understanding-the-arc-cache/#:~:text=Understanding%20the%20defaults,defaulted%20to%2050%25.

Hit rate is just over 90%, which is good, and zfs should release ram if needed, but I can't just ignore the zabbix warnings, and pushing the percentage higher seems just as wrong.

I could set zfs_arc_max but unfortunately that's a fixed value, not a %, so not portable.

Suggestions?

ZFS ate my RAM: Understanding the ARC cache

If you’re running ZFS on Linux and checking your system’s memory usage, you might be shocked to see that most of your RAM appears to be consumed. Don’t panic! This is actually by design, and it’s a good thing. The confusion When you run free -h, you might see something like this: $ free -h total used free shared buff/cache available Mem: 31Gi 28Gi 512Mi 128Mi 2.5Gi 2.8Gi Swap: 8.0Gi 1.

Show thread

Wish the sun to stand still 🌞2d ago

@jonsnow #ZFS #java

R.L. Dane

🍵

2d ago

Umm... WHAT??

rld@Intrepid:scripts$ ls -l jargon
-rwxr-xr-x  1 rld rld 1,443,874 Jun  2 06:51 jargon
rld@Intrepid:scripts$ ls -lh jargon
-rwxr-xr-x  1 rld rld   1.4M Jun  2 06:51 jargon
rld@Intrepid:scripts$ du -sh jargon
981K	jargon

Ok, that's enough computering for today. I can't even. Oh, wait...

It's #ZFS on #FreeBSD, so compression something something??

rld@Intrepid:~$ dd if=/dev/zero count=2048 of=blah1
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.007787 secs (134654119 bytes/sec)
rld@Intrepid:~$ dd if=/dev/urandom count=2048 of=blah2
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.012141 secs (86364101 bytes/sec)
rld@Intrepid:~$ ls -lh blah?
-rw-r--r--  1 rld rld   1.0M Jun  2 06:58 blah1
-rw-r--r--  1 rld rld   1.0M Jun  2 06:58 blah2
rld@Intrepid:~$ du -sh blah?
512B	blah1
1.0M	blah2
rld@Intrepid:~$

YES, COMPRESSION!!! XD

Well...

rld@Intrepid:scripts$ ls -lh jargon
-rwxr-xr-x  1 rld rld   1.4M Jun  2 06:51 jargon
rld@Intrepid:scripts$ du -sh jargon
981K	jargon
rld@Intrepid:scripts$ simplify $(gzip -1 < jargon |wc -c)
668.50 KiB
rld@Intrepid:scripts$

Not GREAT compression, but you know... gift horses! 😆