SCSI sync unsupported: who's guilty?

SCSI sync unsupported: who's guilty?

[Janpieter Sollie]

[-- Attachment #1.1: Type: text/plain, Size: 592 bytes --]

Hi everyone,
During testing of bcachefs with a aacraid controller, I encountered the following issue: The
bcachefs kernel thread reports a critical IO error due to aacraid disabling SCSI command
SYNCHRONIZE_CACHE by default.
Who should handle those cases?
- adapter: does it need to "discard" the invalid CDB and act like it completed successfully?
- aacraid: enable when explicity requested?
- block: does it need to "skip" the block error and move on?
- kernel thread: "ignore" the error?
I have no idea what the proper way to do here would be.  Anyone who does?
Janpieter.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: SCSI sync unsupported: who's guilty?

[Hannes Reinecke]

On 6/25/20 1:51 PM, Janpieter Sollie wrote:
> Hi everyone,
> During testing of bcachefs with a aacraid controller, I encountered the following issue: The
> bcachefs kernel thread reports a critical IO error due to aacraid disabling SCSI command
> SYNCHRONIZE_CACHE by default.
> Who should handle those cases?
> - adapter: does it need to "discard" the invalid CDB and act like it completed successfully?
> - aacraid: enable when explicity requested?
> - block: does it need to "skip" the block error and move on?
> - kernel thread: "ignore" the error?
> I have no idea what the proper way to do here would be.  Anyone who does?
> Janpieter.
> 
> 
This would be more properly redirected to the linux-scsi mailing list;
but anyway I think your problem should be solved by passing the module 
parameter 'aac_cache=6' to the aacraid module.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke            Teamlead Storage & Networking
hare@suse.de                               +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer