On 11/06/2014 05:54 PM, James Bottomley wrote: > > We don't have a failure. This is the problem. Determining that a > problem exists > OK Sorry. I assumed the bridge is smart enough to do nothing, ie READ_CAPACITY_10 is passed as is via sata to the device that actually supports READ_CAPACITY_16, as I understand then the actual good drive is not suppose to send size-modulue-2G in response to READ_CAPACITY_10. Should it ? Then the bridge just sends that back to me, now if I send READ_CAPACITY_16 the bridge will return NOT-SUPPORTED because it is unexpected. But what are you saying that the bridge was smart enough to do READ_CAPACITY_16 get a 64bit value from the drive and then return the lower 32bit to me ? Really ? I would not imagine in the life of me someone so dumb. And surly it is against any spec. Are you sure ? I think you are wrong I think the guy reported that he can only see 2T out of his 3T drive which means the bridge returned 0xffffffff, exactly 2T > James > > But hey, I guess stupidity is limitless, this one here pushing real far. Cheers Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
