[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC 0/4] POC: Generating realistic block errors
From: |
Tony Asleson |
Subject: |
Re: [RFC 0/4] POC: Generating realistic block errors |
Date: |
Thu, 14 Nov 2019 09:47:48 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 |
On 9/20/19 12:28 PM, Tony Asleson wrote:
> On 9/20/19 4:22 AM, Stefan Hajnoczi wrote:
>> blkdebug is purely at the QEMU block layer level. It is not aware of
>> storage controller-specific error information or features. If you want
>> to inject NVMe- or SCSI-specific errors that make no sense in QEMU's
>> block layer, then trying to do it in blkdebug becomes a layering
>> violation. This justifies adding a new error injection feature directly
>> into AHCI, virtio-scsi, NVMe, etc devices.
>
> Good discussion point...
>
> In my opening use case for this POC I'm generically trying to create an
> unrecoverable media error for a specific sector. For each of the
> different device types it's different on how that error is conveyed and
> the associated data in transfer.
>
I would like to get some additional clarification on this point. Should
I be investing more time integrating my proposed functionality into
blkdebug or other?
Sorry for the long response time, got sidetracked with other stuff.
Thanks,
Tony
- Re: [RFC 0/4] POC: Generating realistic block errors,
Tony Asleson <=