How SCSI devices tell you their logical and physical block sizes
Since I spent today looking this up and working it all out, I might as well write all of this down.
Old SCSI had no distinction between logical and physical size; it just had the block size. Modern SCSI has redefined those old plain block sizes to be the logical block size and then added an odd way of encoding the physical block size. This information is reported through the SCSI operation READ CAPACITY (16), which unlike its stunted older brother READ CAPACITY (10) is not actually a SCSI command; instead it's a sub-option of a general SERVICE ACTION IN command. This may assist you in finding it in code and/or documentation.
(SERVICE ACTION IN is SCSI opcode 0x9E and READ CAPACITY (16) is
sub-action 0x10. Nice code will have some
#defines or the like
for these; other code, well, may not. See the discussion of finding
SCSI opcodes and so on in this entry.)
The logical block size is returned as a big endian byte count in response bytes 8 through 11 (counting from 0; 0 through 7 are the device's size in logical blocks, again big endian). The size of physical blocks is reported by giving the 'logical blocks per physical block exponent' in the low order four bits of byte 13. If it is set to some non-zero value N, there are 2^N logical blocks per physical block; for 4k sector disks with 512 byte logical blocks the magic exponent is thus 3.
There is no guarantee that code that uses READ CAPACITY (16) either sets or reads this exponent. My impression is that RC (16) and its use in code predates at least the need to think about the difference and perhaps the actual definition of the field (as opposed to just marking it 'reserved').
Note that some code may talk about or
#define 'READ CAPACITY' when
it means READ CAPACITY (10). You should ignore this code because no
one wants to use RC (10) any more. If there's code that is carefully
handling a device capacity case of '0xffffffff', you're reading the
wrong code. Yes, this can be confusing.
(One of the problems with READ CAPACITY (10) is that the (logical block) size of the device is limited to a 32-bit field. With 512 byte blocks this translates to a disk size of about 2 Tb. It follows that if some old system can't deal with 2 Tb SCSI disks, it's extremely likely that it probably also has no idea of physical block size versus logical block size.)
I'm developing opinions on how storage systems should handle all of this, but that's going to have to wait for another entry.