SudoPacman

Ahh. Okay. Sorry, I don't know much about ZFS.
I just tried `zfs destroy tv` and it says the dataset does not exist.
 
But after checking the output of `zfs --help` I guessed at:
zfs destroy zfs_cache/tv zfs destroy zfs_cache/movies  
And that's done the trick.
Thanks.
 
Still annoying that it does this, but here we are I guess.
 
Thanks for the help.
 
Cheers
 

Got an update on this in case anyone else experiences the same thing.
 
In a nutshell, it kept happening. I'd get through a preclear, then add parity and boom, at some point during the rebuild.
This is on a practically new supposedly enterprise class 16TB drive, so I was suspicious.
 
A mate at work suggested it could be PCIe lanes, since I'm using an older Intel i7 970 and X58 platform, and during a rebuild there is a lot of strain on the system, and I have a lot of drives (10 data plus 2 parity and 2 SSDs).
 
I've been thinking about an upgrade for a while, and have now pulled the trigger on an AM5 based build on an X670.
Expensive, but it's crucial to me that I can trust my server.
 
Just finished a parity rebuild, and all seems good.
 
Hope this helps someone else.
 
Cheers,
Pacman

When future me finds this, again, perhaps I should note the answer rather than have to rediscover it.
 
If set the IP of the network interfaces to automatic, and fix them in your DHCP server, the docker networks get their gateway set correctly.
I changed motherboard, so the MAC address changed, so that's what caused it.
 
Feels like a bug, but the workaround is fine.