Closed hb0nes closed 1 year ago
I've not seen this on 4.19.0-17-amd64 despite a lot of sending, so maybe you can upgrade your way out of your problems?
(Not saying it's not a genuine issue, just offering a data point.)
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.
System information
Distribution Name | Debian Buster Distribution Version | Kernel Version | 4.19.0-8-amd64 Architecture | x86_64 OpenZFS Version |
zfs-2.0.3-8~bpo10+1, kmod-2.0.3-8~bpo10+1
Describe the problem you're observing
We create and sync zfs snapshots every 15 minutes (with pyznap, it just uses zfs send and recv over ssh). ZFS hung on the receiving side - 15 minutes later we received errors on the sending side that the recv process was already (still) running.
Describe how to reproduce the problem
I don't know how. It hasn't happened before. The ZFS version is quite new so it is most likely a (rare) bug.
Include any warning/errors/backtraces from the system logs
The first kernel log stacktrace on the receiving end:
This repeats itself until a new one appears:
After this, no more zfs kernel messages appeared.