Bug 762570 (GLUSTER-838) - Wrong volume size displayed for mirror volume and wrong aggregated volume size
Summary: Wrong volume size displayed for mirror volume and wrong aggregated volume size
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-838
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-21 01:43 UTC by Harshavardhana
Modified: 2015-03-23 01:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Wrong Replicate Volume size (106.97 KB, image/png)
2010-04-20 22:43 UTC, Harshavardhana 		no flags Details
Wrong size on log manager (109.88 KB, image/png)
2010-04-20 22:44 UTC, Harshavardhana 		no flags Details
Zero sized volume size (107.65 KB, image/png)
2010-04-20 22:59 UTC, Harshavardhana 		no flags Details
Wrong Size Displayed after Updating volume properties (109.55 KB, image/png)
2010-04-20 23:00 UTC, Harshavardhana 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Harshavardhana 2010-04-20 22:44:16 UTC 
Created attachment 180 [details]
patch for RedHat's patch :)
Comment 1 Harshavardhana 2010-04-20 22:59:25 UTC 
Another issues

* After updating volume properties values go even bad showing lower fractions.
* Volume Property shows zero. 

Please find the attachment

Reproducibility: Always
Comment 2 Harshavardhana 2010-04-20 22:59:51 UTC 
Created attachment 181 [details]
cleaning diff for .spec file
Comment 3 Harshavardhana 2010-04-20 23:00:23 UTC 
Created attachment 182 [details]
Adds -f to cp invocations to allow build phase by non-root
Comment 4 Harshavardhana 2010-04-21 01:43:48 UTC 
Two problems noted during testing. 

* Mirror volume aggregated size is wrong where it should have showed us 12TB it is showing us 24TB. 
* Again volume size is wrong as when during Volume creation the size was proper since then the value seems to be rounded off and show wrong Gigabytes where as the volume is 24TB. 

This needs to be fixed as it looks odd during demo's. 

Please find the attachment with screenshots.
Note You need to log in before you can comment on or make changes to this bug.