• Paolo Bonzini's avatar
    block: introduce block job error · 32c81a4a
    Paolo Bonzini authored
    The following behaviors are possible:
    
    'report': The behavior is the same as in 1.1.  An I/O error,
    respectively during a read or a write, will complete the job immediately
    with an error code.
    
    'ignore': An I/O error, respectively during a read or a write, will be
    ignored.  For streaming, the job will complete with an error and the
    backing file will be left in place.  For mirroring, the sector will be
    marked again as dirty and re-examined later.
    
    'stop': The job will be paused and the job iostatus will be set to
    failed or nospace, while the VM will keep running.  This can only be
    specified if the block device has rerror=stop and werror=stop or enospc.
    
    'enospc': Behaves as 'stop' for ENOSPC errors, 'report' for others.
    
    In all cases, even for 'report', the I/O error is reported as a QMP
    event BLOCK_JOB_ERROR, with the same arguments as BLOCK_IO_ERROR.
    
    It is possible that while stopping the VM a BLOCK_IO_ERROR event will be
    reported and will clobber the event from BLOCK_JOB_ERROR, or vice versa.
    This is not really avoidable since stopping the VM completes all pending
    I/O requests.  In fact, it is already possible now that a series of
    BLOCK_IO_ERROR events are reported with rerror=stop, because vm_stop
    calls bdrv_drain_all and this can generate further errors.
    Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
    Reviewed-by: default avatarEric Blake <eblake@redhat.com>
    Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
    32c81a4a
blockjob.c 6.52 KB