zfs send -R | zfs recv can fail in the middle due to a snapshot being taken

[rincebrain]

System information

Type	Version/Name
Distribution Name	Debian
Distribution Version	9.3
Linux Kernel	4.9.0-4-amd64
Architecture	amd64
ZFS Version	0.7.3-3
SPL Version	0.7.3-1

Describe the problem you're observing + how to reproduce the problem

When doing a long-running zfs send -R foo/bar/baz@ten | zfs recv -ds newfoo, an automated utility helpfully took a recursive snapshot on newfoo, and zfs recv abruptly died with cannot receive incremental stream: kernel modules must be upgraded to receive this stream. with newfoo/bar/baz having completed snapshots one, ..., seven and throwing that error on attempting to resume.

I would have expected the in-progress receiving dataset(s) to have remained immutable until the receives were completed, but apparently this isn't the case.

Destroying the errant snapshot on newfoo/bar/baz allowed the zfs send to proceed like nothing ever happened.

Since there's already a number of bugs suggesting that this message should be broken out and detailed further (#6547, #6574), this bug is mostly about the fact that nothing is stopping you from shooting yourself in the foot and not being able to discover why without making dramatic leaps or (presumably) reading zfs/dbgmsg.

[stale]

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.

[joshenders]

Is there a way to reopen this? I'm still experiencing this issue on 2.2.2-1~exp1 on Debian 12 6.1.0-15-amd6

[rincebrain]

I think it now outputs a more useful message, something like incremental source differing, but not by much, if I recall.