Description of problem (please be detailed as possible and provide log
snippests):


Doc link - https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.4/html-single/managing_openshift_container_storage/index?lb_target=preview


We have changed the disk sizes and examples for LSO to reflect 2TiB in Bug 1839011. Hence Managing guide also needs similar changes to be in symmetry with deployment guide.

Some points to consider IMO
-----------------------------------

Ideally, a bare metal and VMware LSO clusters can have wide variety of DISKs attached(NVMe, SSD) across different customer setups(based on their hardware) . 

Thus resulting in differences in disk sizes. Hence, OSD sizes may not translate to exact 2 TB (unless we have partitions IN- which is out of scope as of now)

Hence, we need to discuss and then, based on consensus, need to change the 100Gi and other disk sizes in the example outputs of LSO for Managing guide as well.

We can take it up for the next OCS 4.4 async doc release.


Version of all relevant components (if applicable):
OCS 4.4 changes for deployment guide - https://bugzilla.redhat.com/show_bug.cgi?id=1839011


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info: