DatuX

ive created a ticked for those hooks. since it as zfs issue ill close this for now.

yes, it can do that. if you run zfs-autobackup on a 3d host, and specify both --ssh-source and --ssh-target, that host will connect to both hosts via ssh. keep in...

thanks for the coffee :) maybe in future versions, but no time soon.

very nice, however i think its a bit tricky to make the default algorithm dynamic: if one node has xxhash and the other node hasn't , it will look to...

That sounds good, first line as a comment with the "hashing" config? (Things like the hash and chunksize and skip option?)

oh no another silent corruption bug in zfs? :( i think that the header should be read earlier. Blockhasher is a low level function, and by then its too late...

Coincidently the datacorruption bug is also related to sparse handling of files it seems. They just released a fix: https://github.com/openzfs/zfs/releases/tag/zfs-2.1.14

sounds interesting. i'm all for changing the default hash algo to something like xxh64 if thats not a too obscure library. we're still in development/beta anyway, and zfs-check isnt widely...

same goes for a different default block-size and count, i didnt do much testing to choose that. (just guestimated values)

its very cool actually, this is very usefull to test huge volumes :)