[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC 0/4] POC: Generating realistic block errors
From: |
Stefan Hajnoczi |
Subject: |
Re: [RFC 0/4] POC: Generating realistic block errors |
Date: |
Thu, 21 Nov 2019 10:30:12 +0000 |
User-agent: |
Mutt/1.12.1 (2019-06-15) |
On Thu, Nov 14, 2019 at 09:47:48AM -0600, Tony Asleson wrote:
> 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.
blkdebug can inject EIO when a specific LBA is accessed. Is that
enough for what you want to do? Then you can reuse and maybe extend
blkdebug.
Stefan
signature.asc
Description: PGP signature