dear non-Patronizers: February's "See the Sausage Being Made" is now public. https://mwl.io/archives/24612
includes a reveal of the #openzfsmastery cover painting!
Ground out some words on #openzfsmastery today, discussing lopsided pools and self-healing. Also got tomorrow's #60SecondsOfWIP recorded!
I'd appreciate your help keeping the lights on while I finish this book. https://sponsor.mwl.io
Today in #openzfsmastery: re-re-redrafted the section on block size, then discussed ashift autodetection, stripes, and mirrors.
Want to help me keep the lights on while I scribble this silly thing? https://sponsor.mwl.io
Finally getting back to my 72-disk draid bhyve VM for #openzfsmastery.
Turns out that setting ahci_device_limit="8" in the vm-bhyve config let it boot just fine.
Thank you everyone for your suggestions, but especially @dch for this one!
spent the day arguing with debian and bhyve. finally got to crack open the #openzfsmastery manuscript and discovered: my brain is done.
It's Friday. I'm gonna knock off a bit early, fold some laundry, do some dishes, and go to the dojo.
My boss is gonna hate it, but to hell with that guy.
I'm trying to test draid virtually for #openzfsmastery, because nobody's gonna give me a shelf of 60 disks to play with. I set everything up like:
disk35_name="disk35"
disk35_type="ahci-hd"
disk35_dev="sparse-zvol"
Seems that if I have 35 ahci-hd entries, disk0 through disk34, bhyve and freebsd works. At disk35, the host panics on boot.
Is this expected with bhyve? Or does FreeBSD need a special tweak with 36 disks?
Michael W Lucas 