#openzfsmastery

Support rodent indolence! Sponsor #openzfsmastery https://www.tiltedwindmillpress.com/product/openzfs-sponsor/ @mwl@io.mwl.io RE: https://io.mwl.io/@mwl/117576257070930573

My Saturday: scrambling to finish #openzfsmastery. Their #Raturday: this. We are not the same. #petRats #rats

"Routinely taking snapshots more frequently than once every five seconds can disrupt the normal flow of transaction groups and conflict with the I/O scheduler and the write throttler. See Chapter 17 for more information but seriously, WHY are you trying to take snapshot every second of every hour, all day, every day?" Grinding on #openzfsmastery to get something to tech review before my surgery knocks me out for the rest of the year. I would appreciate your support.

#OpenZFS includes arcstat, their standard tool to interrogate ARC stats. It's in python, so #FreeBSD doesn't install it. It'd be really nice to have this as a package before #openzfsmastery comes out.

That's #openzfsmastery Chapter 15, on caches, done! Like the October "See the Sausage Being Made" post says, nothing concentrates the mind like the prospect of being hanged...

maybe I should quit writing and go make dinner? No, I'm short on time to finish #openzfsmastery and the PHP Apocalypse cost me a bunch of it. No food! Only write!

wrote about send:encrypted, which should make @dexter@bsd.network happy. #openzfsmastery

Me, 4PM: "dang it, why is my incremental zfs send of /var/mysql sending the entire file instead of just the changes from yesterday???" Me, now: "Oh. The contents of /var/mysql churn 99% between yesterday and today." Anyway, I'm working hard on #openzfsmastery. I'd appreciate your support.

"As the old saying goes: everybody has a test environment. Some people are lucky enough to have a separate environment to run production in." #openzfsmastery #footnote

I used to call it "rubber hose cryptography" or "kneecap cryptography" or any number of things in an effort to avoid spelling out the real threat. People didn't get it. I think I'll start calling it an "XKCD 538 attack" instead. Anyone who doesn't look it up isn't my reader. #openzfsmastery

"If you cannot consistently type your passphrase correctly twice in a row, consider a simpler passphrase. If you can consistently type your passphrase correctly any number of times in a row, get a more complex one." #openzfsmastery #footnote I'd appreciate help finishing this book. mwl.io/sponsor

Today in #openZFSmastery: "Lucas can now manage his own mistakes. Jude, of course, must manage the mistake of giving Lucas a jail." I'd appreciate your support writing this book.

Today's #60SecondsOfWIP is out! From #OpenZFSMastery: "Lucas is Incompetent or Evil." At https://mwl.io/archives/24997 or wherever mediocre podcasts are sold.

Writing about containers and jails today for #openzfsmastery. Language management is a big part of writing a tech book. Techies are both notoriously bad at language, and notoriously picky about it. Containers and jails are types of lightweight virtual machines. I don't want to keep repeating "lightweight virtual machines" multiple times in a paragraph, so I need a good short punchy word. I could abbreviate and call them LVMs, but Linux folks have different associations for that abbreviation. The current attempt is to call them "lightweight virtual machine instances" 2-3 times to build an association in the reader's brain, then call them "instances" for the remainder of the chapter. It wouldn't work for a longer piece, but I think I can get away with it for half a chapter.

Got the #openzfsmastery section on privilege delegation completed. Tomorrow, I figure out delegating datasets to containers. Seems there's little integration, everything gets delegated by hand? Sponsorships are still open on this silly thing:

okay, I got the #openzfsmastery boot loader chapter fixed. Definitely done now. Calling it for the day. Take a few hours off this evening to read to the rodents.

Me, this morning: Yay, I finished the #openzfsmastery boot environment chapter yesterday, I can move on. Me, getting to desk and seeing the boot environment chapter: oh no.

that's the Boot Environment chapter of #openzfsmastery done! Covers FreeBSD and Proxmox. I think my Saturday's done. It's pajama time.

#bhyve with #ZFS rollback makes testing boot environments for #openzfsmastery sooo much easier. Snapshots on the hypervisor. Snapshots in the VM. Snapshots EVERYWHERE. #sysadmin

Working on #openzfsmastery, trying to fake boot environments with Proxmox. Because Proxmox integrates ZFS as a first-class filesystem. It's going swimmingly. You can donate to extend my suffering.