Re: Invalid optimal transfer size 33553920 accepted when physical_block_size 512

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bernhard,

> # sg_readcap /dev/sdc
> READ CAPACITY (10) indicates device capacity too large
>   now trying 16 byte cdb variant
> Read Capacity results:
>    Protection: prot_en=0, p_type=0, p_i_exponent=0
>    Logical block provisioning: lbpme=0, lbprz=0
>    Last LBA=15628053166 (0x3a3812aae), Number of logical blocks=15628053167
>    Logical block length=512 bytes
>    Logical blocks per physical block exponent=3 [so physical block
> length=4096 bytes]
>    Lowest aligned LBA=0
> Hence:
>    Device size: 8001563221504 bytes, 7630885.3 MiB, 8001.56 GB, 8.00 TB

I sent a patch that I would like you to test. It adds some additional
sanity checking to the block limits handling. Given the VPD output you
sent earlier, I am hoping it will work around the issue.

I still can't explain how the physical block size can be unset given
that it is reported by the device and the capacity is > 0xffffffff. I
even tried to tweak scsi_debug to see if somehow the no_read_capacity_16
flag for card readers happened to be set in your case and caused us to
go down the wrong path. But no. I'm stumped.

Do you have any READ CAPACITY errors or messages in your log? There were
none in the output you sent.

-- 
Martin K. Petersen	Oracle Linux Engineering




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]

  Powered by Linux