Errata #4 doesn't mention non-destructive mitigation option

[JMoVS]

System information

Type	Version/Name
Distribution Name
Distribution Version
Linux Kernel
Architecture
ZFS Version	0.8.0 rc4
SPL Version

Describe the problem you're observing

@behlendorf Recently clarified how Errata #4 is actually processed in this comment:

#8625 (comment)

from there:

Deleting all the snapshots on the original source pool should be sufficient. The reason is that the fundamental fix for raw send issue was to associate an "IVset guid" with each snapshot. It acts as an identifier for the set of IVs used to encrypt a given snapshot and is now required during a raw receive. Since snapshot are immutable by design this "IVset guid" couldn't be associated with existing snapshots.

The errata will be reported in zpool status when either:

1. The `bookmarks_v2` feature has not been enabled, or

2. A snapshot is detected without the required "IVset guid"

If nothing is reported then all the snapshots in your encrypted pool do include the "IVset guid". I hope that helps clear things up.

If this fact was to be communicated more clearly, it could help people who have top-level encrypted datasets and who don't want to destroy their whole pools, as mentioned in this comment of mine:
#8308 (comment)

Describe how to reproduce the problem

Simply creating new snapshots and deleting old ones is sufficient to get rid of the warning.