Mark Maybee wrote: > Darren J Moffat wrote: >> For an encrypted dataset it is possible that by the time we arrive in >> zio_write() [ zio_write_encrypt() ] that when we lookup which key is >> needed to encrypted this data that key isn't available to us. >> >> Is there some value of zio->io_error I can set that will not result in >> a panic ? but will put the write in to some state where we can try >> again later - I guess not just this write but maybe the whole >> transaction group ? >> > No, we have no ability to do this. With George's fix for 6565042, we > will introduce the ability to "hang" the pool on an IO failure... this > may give you what you want.
It might well do, but will it allow "unhanging" later ? I couldn't tell much from that bug unfortunately. -- Darren J Moffat
