Antonio Russo

@jgoerzen Can you 1. Capture the `zpool events -v` report when one of these "bad" snapshots is created? 2. Try to zfs send that snapshot (i.e., to `zfs send ......

@cbreak-black Was there a system restart between the occurrence of the corrupted snapshot and the problems? Restarting has "fixed" this symptom for me (though you will need to scrub twice...

@InsanePrawn I can't seem to find commit 4d5b4a33d in any repository I know of (and neither can github, apparently, either). However, in your report you say this was a "recent...

@InsanePrawn Does running the zrepl workload reproduce the bug on 2.0.5 (or another recent release?) I don't think the snapshot is terribly important --- unless you're able to really dig...

@cbreak-black Can you enable the all-debug.sh ZEDlet, and put the temporary directory somewhere permanent (i.e., not the default of `/tmp/zed.debug.log`)? This will get the output of `zpool events -v` as...

@phreaker0 Unfortunately, the bug that da92d5c introduced (#10737) was fixed by #12299, which I believe is present in all maintained branches now. It does not fix #11688, (which I suspect...

@AndrewJDR 1. Are the affected datasets encrypted? 2. Do you get the `Permanent errors have been detected in the following files` line? 3. Does the "corruption" go away after rebooting...

A signed git tag is very easy for me to verify, so I'd be happy with that (I'd prefer it).

@jcwinkler I share you concern over any unnecessary exposure of the secret key, so I'm an advocate of your second approach: tagging locally, and then having that push trigger the...

@behlendorf I'm trying to dig into this a little bit further. I want to rule out in-flight corruption of snapshot data, so I'd like to be able to get access...