-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
regression with "Add display of checksums to zdb -R" #9644
Labels
Type: Defect
Incorrect behavior (e.g. crash, hang)
Comments
cc @behlendorf |
cc @PaulZ-98 |
Thanks for reporting this. I will have to use another zio for zio_checksum_compute instead of the destroyed one. |
PaulZ-98
added a commit
to datto/zfs
that referenced
this issue
Dec 2, 2019
The checksum display code of zdb_read_block uses a zio to read in the block and then calls zio_checksum_compute. Use a new zio in the call to zio_checksum_compute not the zio from the read which has been destroyed by zio_wait. Signed-off-by: Paul Zuchowski <pzuchowski@datto.com> Fixes openzfs#9644
12 tasks
PaulZ-98
added a commit
to datto/zfs
that referenced
this issue
Dec 2, 2019
The checksum display code of zdb_read_block uses a zio to read in the block and then calls zio_checksum_compute. Use a new zio in the call to zio_checksum_compute not the zio from the read which has been destroyed by zio_wait. Signed-off-by: Paul Zuchowski <pzuchowski@datto.com> Fixes openzfs#9644
PaulZ-98
added a commit
to datto/zfs
that referenced
this issue
Dec 2, 2019
The checksum display code of zdb_read_block uses a zio to read in the block and then calls zio_checksum_compute. Use a new zio in the call to zio_checksum_compute not the zio from the read which has been destroyed by zio_wait. Signed-off-by: Paul Zuchowski <pzuchowski@datto.com> Fixes openzfs#9644
behlendorf
pushed a commit
that referenced
this issue
Dec 3, 2019
The checksum display code of zdb_read_block uses a zio to read in the block and then calls zio_checksum_compute. Use a new zio in the call to zio_checksum_compute not the zio from the read which has been destroyed by zio_wait. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Igor Kozhukhov <igor@dilos.org> Signed-off-by: Paul Zuchowski <pzuchowski@datto.com> Closes #9644 Closes #9657
tonyhutter
pushed a commit
to tonyhutter/zfs
that referenced
this issue
Dec 26, 2019
The checksum display code of zdb_read_block uses a zio to read in the block and then calls zio_checksum_compute. Use a new zio in the call to zio_checksum_compute not the zio from the read which has been destroyed by zio_wait. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Igor Kozhukhov <igor@dilos.org> Signed-off-by: Paul Zuchowski <pzuchowski@datto.com> Closes openzfs#9644 Closes openzfs#9657
tonyhutter
pushed a commit
to tonyhutter/zfs
that referenced
this issue
Dec 27, 2019
The checksum display code of zdb_read_block uses a zio to read in the block and then calls zio_checksum_compute. Use a new zio in the call to zio_checksum_compute not the zio from the read which has been destroyed by zio_wait. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Igor Kozhukhov <igor@dilos.org> Signed-off-by: Paul Zuchowski <pzuchowski@datto.com> Closes openzfs#9644 Closes openzfs#9657
tonyhutter
pushed a commit
that referenced
this issue
Jan 23, 2020
The checksum display code of zdb_read_block uses a zio to read in the block and then calls zio_checksum_compute. Use a new zio in the call to zio_checksum_compute not the zio from the read which has been destroyed by zio_wait. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Igor Kozhukhov <igor@dilos.org> Signed-off-by: Paul Zuchowski <pzuchowski@datto.com> Closes #9644 Closes #9657
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System information
Describe the problem you're observing
regression with "Add display of checksums to zdb -R" in 894f669
this commit introduce test
zdb_checksum.ksh
and in failed on DilOS with:try to parse core file we can see:
based on info, first address with
zio_t *zio
has been freed in functionDescribe how to reproduce the problem
run ZTS and check logs:
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: