Bug 2186798 - [DDF] The unit prefix used in these paragraphs are wrong, but is a common mistake. The IEEE 802.3 Ethernet standard [NEEDINFO]
Summary: [DDF] The unit prefix used in these paragraphs are wrong, but is a common mis...
Keywords:
Status: RELEASE_PENDING
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 5.0
Hardware: All
OS: All
medium
low
Target Milestone: ---
: Backlog
Assignee: Anjana Suparna Sriram
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-14 14:32 UTC by Direct Docs Feedback
Modified: 2023-08-03 11:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
lysanche: needinfo? (msaini)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6465 0 None None None 2023-04-14 14:34:32 UTC

Description Direct Docs Feedback 2023-04-14 14:32:33 UTC
The unit prefix used in these paragraphs are wrong, but is a common mistake.  The IEEE 802.3 Ethernet standard uses (b)its as the unit prefix to measure port speeds and not (B)ytes.

This documentation also differs from upstream documentation.

For example

Upstream:
link: https://docs.ceph.com/en/latest/start/hardware-recommendations/#speed

"It takes three hours to replicate 1 TB of data across a 1 Gb/s network and it takes thirty hours to replicate 10 TB across a 1 Gb/s network."

Red Hat Documentation with the incorrect unit prefix and incorrect timeline:

"In the case of a drive failure, replicating 1 TB of data across a 1 GB Ethernet network takes 3 hours, and 3 TB takes 9 hours."

Reported by: jherron

https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/5/html/installation_guide/red-hat-ceph-storage-considerations-and-recommendations#annotations:2b83c5dc-aa8c-4ae6-ba4e-7feb49c68593

Comment 1 RHEL Program Management 2023-04-14 14:32:40 UTC
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.


Note You need to log in before you can comment on or make changes to this bug.