Event JSON
{
"id": "e12e7a6f0e3153ec9087ce3bada700a85c2be9c99046b667e97ace932c26e222",
"pubkey": "d22d3e7a3748f64d667c85f6bc02a4e12d1dfdfdcf5b6f2654bf42e847797112",
"created_at": 1730078129,
"kind": 1,
"tags": [
[
"p",
"f0332c2dbed4b678113b0d9b9acffc1d7ac229375ddd6f5098ca896cc1e71025",
"wss://relay.mostr.pub"
],
[
"p",
"75c4441558d260c0ca589ce8fa89fd5052eccf0b09fca823796810a986ad1c8e",
"wss://relay.mostr.pub"
],
[
"e",
"e9222b6316dec7ad16e890837bbbf3be12e77b4b1235be6c67681e38e1c9a213",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/cks/statuses/113382400286243222",
"activitypub"
]
],
"content": "nostr:npub17qejctd76jm8syfmpkde4nlur4avy2fhthwk75yce2ykes08zqjs3gv7la The whole ZFS shutdown and boot process is arcane and not really documented (eg, that ZFS does not actually export pools on shutdown). The 'zfs.cache' file has a single name for each disk, and if the disk isn't there, you lose on boot as ZFS won't start the pool. There's no good way apart from abandoning zfs.cache, as suggested by others, and using zfs-import-scan.service.\n\n(It was worse on Solaris, where the kernel itself magically loaded zfs.cache and did things with it.)",
"sig": "aa9e7c8a073b797fc9e9e86d077fbc28182912bbea3905e9ef07737e3451f26533eaf336cddc3311b3603cd82cfe25e19273b3f84a9a0ddffba85fbde337c3db"
}