UASP
USB Attached SCSI Protocol (UASP) transports SCSI commands over USB and supports multiple outstanding commands, without by itself guaranteeing throughput, SMART pass-through or durable writes.
UAS separates command submission from completion and can keep multiple commands outstanding. In a normal BOT sequence, the host instead waits for the preceding command's status before sending another command wrapper. These are transport choices, not USB connector shapes or guarantees of a particular transfer rate. [2] [5]
Linux v6.12 registers the uas driver separately from usb-storage. Its abort callback returns FAILED without sending a device abort; a separate recovery handler attempts a USB device reset. An abort or reset message identifies recovery, not a defective bridge or a healthy disk. The usb-storage.quirks flag u prevents UAS binding, whereas t blocks ATA(12)/ATA(16) pass-through on UAS: driver selection and health-data visibility are different capabilities. These are pinned implementation details, not a universal restriction of the protocol. [2] [3]
Relations
Advantages
- Command queuing can provide concurrency when the host, bridge and device support it.
Limitations
- A timeout does not identify a failed component or prove a write never executed.
- Disabling UAS can change error-recovery behavior without fixing the underlying fault.
Citations
- Linux v6.12: UAS driver implementation
- Linux v6.12: usb-storage.quirks
- USB-IF: Mass Storage Bulk-Only Transport revision 1.0, sections 3.3-3.5, 5 and 6