Re: raid5-cache: deeply broken (with write-back?)

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

 





On 08/28/2018 12:24 PM, Daniel Santos wrote:

Yes, that's why I included both the G value and G.  More precisely
29260513280 bytes, which is the 57149440 sectors.  It hasn't exhibited
any failures, but considering its price I'm going to try to RMA it.
They even have a 30GB product and I would still claim false advertising
if I got 29.26GB.

Daniel

This was litigated more than a decade ago.  See http://www.foxnews.com/story/2006/06/28/western-digital-settles-hard-drive-capacity-lawsuit.html and others.  Specifically from the article

"Western Digital Corp. is offering free software to about 1 million consumers to resolve a class-action lawsuit alleging that its computer hard drives stored less material than promised — a discrepancy stemming from the high-tech industry's differing standards for sizing up digital data."

I am not singling out WD for this, rather this is a very well known and well understood unit conversion problem, as well as a formatted capacity issue.   Here is an entry from their FAQ: https://support.wdc.com/knowledgebase/answer.aspx?ID=615

Pretty much all drives sold over last 10+ years include a disclaimer such as this (from an HGST data sheet)

"One megabyte (MB) is equal to one million bytes, one gigabyte (GB) is equal to 1,000MB (one billion bytes), and one terabyte (TB) is equal to 1,000GB (one trillion bytes) when referring to storage capacity. Accessible capacity will vary from the stated capacity due to formatting, system software, and other factors"



--
Joe Landman




[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux