Skip to content
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.

Sign up for GitHub

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

Jump to bottom

nopwrites on dmu_sync-ed blocks can result in a panic #8957

Merged
merged 1 commit into from
Jun 28, 2019
Merged

nopwrites on dmu_sync-ed blocks can result in a panic #8957

merged 1 commit into from
Jun 28, 2019

Commits on Jun 27, 2019

  1. nopwrites on dmu_sync-ed blocks can result in a panic 

    After device removal, performing nopwrites on a dmu_sync-ed block
will result in a panic. This panic can show up in two ways:
1. an attempt to issue an IOCTL in vdev_indirect_io_start()
2. a failed comparison of zio->io_bp and zio->io_bp_orig in
   zio_done()
To resolve both of these panics, nopwrites of blocks on indirect
vdevs should be ignored and new allocations should be performed on
concrete vdevs.

Signed-off-by: George Wilson <gwilson@delphix.com>
    @grwilson
    grwilson committed Jun 27, 2019
    Configuration menu
    Copy the full SHA
    0f7a60b View commit details
    Browse the repository at this point in the history