Summary: | diskinfo(8): diskinfo -v shows inacurate drive size | ||||||
---|---|---|---|---|---|---|---|
Product: | Documentation | Reporter: | Ronald F. Guilmette <rfg> | ||||
Component: | Manual Pages | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
Status: | Open --- | ||||||
Severity: | Affects Only Me | CC: | doc, rfg | ||||
Priority: | Normal | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Ronald F. Guilmette
2013-03-29 01:00:00 UTC
Isn't this the classic case of the OS using a base of 1024 to calculate size and the hard drive manufacturer using 1000 for the same purpose? My "3TB" Western Digital Drives show 3.0 TB using smartctl -a and 2.7 TB using diskinfo -v. I get the same 2.7 TB when I manually divide the media size in bytes by 1024 four separate times. Respectfully, Jason Unovitch In message <51C876FF.4030302@gmail.com>, you wrote: >Isn't this the classic case of the OS using a base of 1024 to calculate >size and the hard drive manufacturer using 1000 for the same purpose? I do not believe so, no. It has been awhile since I filed this PR, but I believe that the non-matching numbers I was looking at were sector counts... NOT byte counts. The number of sectors on a drive is the number of sectors on that drive. It should not be different between different tools one might use to look at that number. For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped |