zpool status -v doesn't report all affected files

This is related to #4047, but warrants a separate bug. During this event, I had following situation:

• see errors: 6331 data errors, use '-v' for a list in output of zpool status
• run zpool status -v, get a list of files, remove them
• run zpool status -v again to verify that all lists are replaced with hex ids (what are those exactly btw? :)
• run zpool scrub, wait for it to finish
• find a smaller number of data errors in zpool status -v output, containing paths to the same files as the ones referenced before, but present in a snapshot.

By "same" I mean essentially files that were created on a particular zfs volume on timestamp X, then snapshotted a number of times, without ever being modified. As I understand, in this case you'd have multiple paths pointing at the same data structure describing the contents of the file.

After chatting about this on IRC, my suspicion was confirmed - while scrub is finding all of those references to corrupted data, it most likely displays only a single path. In my case, I went through 5 scrub/cleanup cycles before I've noticed this pattern.