[
https://issues.apache.org/jira/browse/TS-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
B Wyatt updated TS-1163:
------------------------
Attachment: blkgetsize64.v2.bwyatt.patch
It is a good thing I didn't! It had a bug.
Turns out the old 32bit ioctl's units was 512byte blocks, hence the adjustment
based on the hardware sector size.
the 64 bit ioctl's unit is not coerced (and completely different), so it can
ignore the adjustment.
the v2 patch reflects this and supports large disks with sector size > 512.
> Raw disks with more than (2^32)-1 sectors (usually 2TB) are not supported on
> linux
> ----------------------------------------------------------------------------------
>
> Key: TS-1163
> URL: https://issues.apache.org/jira/browse/TS-1163
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
> Reporter: B Wyatt
> Assignee: B Wyatt
> Fix For: 3.3.0
>
> Attachments: blkgetsize64.bwyatt.patch, blkgetsize64.v2.bwyatt.patch
>
>
> Due to 32bit integers in both the trafficersever code and the ioctl used to
> determine raw disk size, the number of sectors reported to the cache storage
> system is bound to 0-0xFFFFFFFF. If a disk has 512 byte sectors and is
> larger than 2TB it will report (num_sectors % 0xFFFFFFFF) * 512 bytes
> avaliable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
