| commit | 1f5bf96001469a61e6da576456bde2a7dee9c40f | |
| author | Rich Ercolani <214141+rincebrain@users.noreply.github.com> | |
| Tue, 16 Jan 2024 21:16:08 +0000 (16 16:16 -0500) | ||
| committer | GitHub <noreply@github.com> | |
| Tue, 16 Jan 2024 21:16:08 +0000 (16 13:16 -0800) | ||
| tree | 0986f425c7ec65e4ccd55b470bfa8bfa7fb3555f | treesnapshot (tar.gz zip) |
| parent | 995734ed12de767f98e1c02ba39efe9595e710b8 | commitdiff |
Make zdb -R a little more sane.
zdb -R has a minor flaw in which it will not always print the full
output of a decompressed block. Oops.
While I was in there, I also reworked the logic so it won't try
ZLE unless everything else fails, which will hopefully avoid the
problem ZDB_NO_ZLE was intended to mitigate of reporting a lot of
false positives of ZLE compressed blocks...
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Rich Ercolani <rincebrain@gmail.com>
Closes #15723
zdb -R has a minor flaw in which it will not always print the full
output of a decompressed block. Oops.
While I was in there, I also reworked the logic so it won't try
ZLE unless everything else fails, which will hopefully avoid the
problem ZDB_NO_ZLE was intended to mitigate of reporting a lot of
false positives of ZLE compressed blocks...
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Rich Ercolani <rincebrain@gmail.com>
Closes #15723
| cmd/zdb/zdb.c | diffblobblamehistory |