The Federation’s computers on Star Trek probably run a ZFS descendant.¹
¹ Cardassians run ReiserFS. #openzfsmastery #rejectedFootnote
openzfsmastery
Churning through the #openzfsmastery
dataset chapter. Progress happened today!
I'd appreciate your support in making this book happen. https://mwl.io/sponsor
Today in #openzfsmastery: replacing failed drive s0d1-NCC-1701D with new drive s0d5-NCC-1701E.
Yes, I'm easily amused. Or desperate for amusement. One of those.
Anyway, you could sponsor this thing and help me feed the rats while I finish writing it. https://mwl.io/sponsor
"Properly written setuid programs are not risky. That's why real setuid programs are risky."
Progress on #openzfsmastery today! Hoping to finish the dataset chapter tomorrow. (Great. Now I've jinxed it.)
Want to help me survive writing this? https://mwl.io/sponsor
"Yes, you could replace all the disks simultaneously, if you’d like to shatter your day with a glorious festival of I/O contention." #openzfsmastery
Wrote about log and cache devices today, and expanding pools by replacing disks with larger disks.
The book is underway! I'd appreciate your help keeping the lights on as I finish it. https://mwl.io/sponsor
I label disks in my ZFS pools by serial number, eg:
$ zpool status vm
pool: vm
state: ONLINE
config:
NAME STATE READ WRITE CKSUM
vm ONLINE 0 0 0
gpt/WD-WCC4N0JSJDKF ONLINE 0 0 0
gpt/WD-WMC4N0M8NRXM ONLINE 0 0 0
But that's unreadable in a book.
Our earlier ZFS books used labels like zfs0, zfs1, etc.
Tempted to use slot0, slot1, etc to be more realistic. But then someone will use that as an actual labeling scheme and complain to us when it bites them. #openzfsmastery
Me: I'm gonna write #openzfsmastery in order. No bouncing around in the manuscript, just clean text from beginning to end!
Also me: My test host needs the new compatibility flag for the root pool. I guess I better jump ahead four chapters and write that. 
#sysadmin #writing
Wrote about #openzfs quotas, reservations, and compression for #openzfsmastery today.
I'd appreciate your support making this book happen. https://mwl.io/sponsor
working on #openzfsmastery performance vs resilience section.
Thinking that the fault tolerance of a 3-disk striped VDEV can best be described as "yeet." #sysadmin
This beast is open for sponsorship. https://mwl.io/sponsor
Thanks to USPS price increases, I will be increasing the cost of #openzfsmastery sponsorships this week.
Grab now if you want them cheap.
Polishing the #openzfsmastery chapter on zvols and virtualization, and came across this:
"Windows in particular has low distress tolerance."
It's rare that I write a perfect sentence, but it does happen.