On 12/04/2015 09:55 AM, Ján Tomko wrote:
> On Fri, Dec 04, 2015 at 09:44:20AM -0500, John Ferlan wrote:
>>
>>
>> On 12/04/2015 08:46 AM, Ján Tomko wrote:
>>> On Tue, Nov 24, 2015 at 03:57:14PM -0500, John Ferlan wrote:
Similar to the openflags VIR_STORAGE_VOL_OPEN_NOERROR processing, if
On Fri, Dec 04, 2015 at 09:44:20AM -0500, John Ferlan wrote:
>
>
> On 12/04/2015 08:46 AM, Ján Tomko wrote:
> > On Tue, Nov 24, 2015 at 03:57:14PM -0500, John Ferlan wrote:
> >> Similar to the openflags VIR_STORAGE_VOL_OPEN_NOERROR processing, if some
> >> read processing operation fails, check
On Tue, Nov 24, 2015 at 03:57:14PM -0500, John Ferlan wrote:
> Similar to the openflags VIR_STORAGE_VOL_OPEN_NOERROR processing, if some
> read processing operation fails, check the readflags for the corresponding
> error flag being set. If so, rather then causing an error - use VIR_WARN
> to flag
On 12/04/2015 08:46 AM, Ján Tomko wrote:
> On Tue, Nov 24, 2015 at 03:57:14PM -0500, John Ferlan wrote:
>> Similar to the openflags VIR_STORAGE_VOL_OPEN_NOERROR processing, if some
>> read processing operation fails, check the readflags for the corresponding
>> error flag being set. If so,
Similar to the openflags VIR_STORAGE_VOL_OPEN_NOERROR processing, if some
read processing operation fails, check the readflags for the corresponding
error flag being set. If so, rather then causing an error - use VIR_WARN
to flag the error, but return -2 which some callers can use to perform
