Christoph Klaffl
Christoph Klaffl
seems like the cache update lock didn't got removed after a sanoid run: please post the output of `ps -p 913700 -o args=` and then remove both lockfiles and run...
@jimsalterjrs what do you think? imho it isn't worth the effort as snapshots are very cheap.
@abrasive i don't think that we will add this, with the implemented of block cloning this may also be not working as expected. I don't know i a blocked clone...
I could reproduce your issue (I have the same setup as you) but this isn't an issue with syncoid, it's a zfs thing, i searched and found a comment explaining...
Yeah sure, a workaround can be implemented. But in my view unmounting before replication is not what the user expects (replication target can still be used for read only stuff....
interesting but I can think of two problems: 1. there is a command character limit, if there are many datasets this may lead to a situation where the command fails...
1) I also don't know if older zfs commands support to specify multiple pools so we need a fallback any way. Can you add an error check for the new...
@jimsalterjrs ready
@danboid @davemosk this is already fixed in master
@NicholasRush if a snapshot is being used in an ongoing send it can't be destroyed AFAIK and zfs will return an "busy" error.