Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

363
active users

toad.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#zfs

12 posts12 participants0 posts today
Public
fuuma

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
Public
Jason Tubnor 🇦🇺
@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.
Public
Juno

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.

#ZFS
Public
Mike

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

Graph showing a scrub take about 19 hours. The max speed is around 700 MB/sec and declines over the time period to around 500 MB/sec
Graph showing disk reads starting near 1 GB/sec and declining to around 500MB/sec over the course of about 15 hours.
#zfs#openzfs
Public *
lw

i'm looking for a new HBA for my FreeBSD file server, is the LSI SAS3416 a reasonable choice?

it seems to be supported by the mps(4) driver and does both SAS/SATA and PCIe, and has PCIe 3.1 for the host interface, so i'm assuming it's a reasonable upgrade for my current LSI SAS2008.

(i mostly just want more ports, but more performance and the ability to use NVMe disks would be nice too.)

edit: i received one good report on the 3416 and one bad report, so i bought one, we will see how it goes.

#freebsd#zfs
Public
Skyr

Ich hadere gerade mit einer Rechner-Neuinstallation (Linux). Ich hätte gerne verschlüsselte Daten (Homeverzeichnis), und ich hätte gern #ZFS. Das ganze soll während des Bootvorgangs entsperrt werden. Was macht "man" denn da heute?

LUKS-verschlüsselte Partition, und dadrin ZFS? Oder ZFS mit dessen nativer (aber eingeschränkter und dem Gefühl nach von Distros weniger supporteter) Verschlüsselung?

Public
John-Mark Gurney

Also, am I the only one that is annoyed that `zpool list -v` lists log and cache devices at the "top level" despite being part of a pool?

they go:
```
poolname
raidz1
drivea
driveb
drivec
log
type
drived
cache
type
drivee
```

instead of putting a couple spaces in front of log and cache so that they are clearly part of poolname.

#FreeBSD#ZFS
Public
John Federico ⌘

For the past month, I have been flitting about from one project to another as my ADHD sees fit. Today, that MO has to end if I'm ever going to complete this #homelab setup.

So, in order, I have to:

* Back up all my LXC's
* Install RAM in a Mac mini
* Reinstall ProxMox with #ZFS on all 3 minis
* Format a bunch of spinning rust disks
* Mount those spinning rust drives in a #Thunderbolt array
* Configure #CEPH
* Restore my LXC's

I figure I'll be done around midnight? Maybe? Fingers crossed.

Replied in thread
Public
Karl Voit :emacs: :orgmode:

@janl The purpose is to warn bystanders to invest in technological #complexity that seems to be very attractive for its advanced features without acknowledging the risks or efforts associated.

Its learning curve doesn't even allow for an easy start.

As with so many awesome tools, this is something for specific experts and not for new/occasional/advanced users.

BTDT and I've had my fair share of bad experiences.

Current pain in my setup: #NixOS. Instead of providing an abstraction layer to keep away certain OS setup & maintenance problems for good, I got into so many little & bigger troubles that I try to tell people only to use it when they are ready to invest its required learning effort all the way.

From my point of view, this also holds true for "advanced" file systems like #ZFS, #XFS, ... YMMV.

#PIM#technology#nix
ExploreLive feeds
About