Bug 1158276 - ssm list shows incorrect pool used size
Summary: ssm list shows incorrect pool used size
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: system-storage-manager
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukáš Czerner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-29 02:02 UTC by Chris Murphy
Modified: 2015-12-02 16:26 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 04:34:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
ssm list, btrfs fi show, btrfs fi df, df (6.69 KB, text/plain)
2014-10-29 02:02 UTC, Chris Murphy
no flags Details

Description Chris Murphy 2014-10-29 02:02:39 UTC
Created attachment 951607 [details]
ssm list, btrfs fi show, btrfs fi df, df

Description of problem: ssm list shows btrfs volume "used" size the same as "total". Affects both Fedora 20 and 21.


Version-Release number of selected component (if applicable):
Test 1
system-storage-manager-0.4-5.fc21.noarch
kernel-3.18.0-0.rc2.git1.1.fc22.x86_64
btrfs-progs-3.17-1.fc21.x86_64.rpm 

Test 2
system-storage-manager-0.4-4.fc20.noarch
kernel-3.16.6-203.fc20.x86_64
btrfs-progs-3.16.2-1.fc21.x86_64 



How reproducible:
Always. Doesn't matter if it's a single volume or raid volume.


Steps to Reproduce:
1. ssm list

Actual results:

btrfs1= raid1 volume made from 2 devices
fedora_klink = single device volume

Pool          Type   Devices       Free       Used      Total  
-------------------------------------------------------------
btrfs1        btrfs  2        530.31 GB  763.85 GB  763.85 GB  
fedora_klink  btrfs  1        271.11 GB  274.12 GB  274.12 GB  
-------------------------------------------------------------



Expected results:

Used for btrfs1 should be ~467.08GiB
Used for fedora_klink should be ~3.12GiB

Since kernel 3.17, the df computation of space is different and has some bugs so I don't know whether pool should report total volume size or if it's raid1 cut the amounts by 1/2 like for md/lvm raid.

Additional info:

btrfs fi show
Label: 'fedora_klink'  uuid: ce8a09b9-44a4-4df7-92c4-3507a2192851
	Total devices 1 FS bytes used 3.12GiB
	devid    1 size 274.12GiB used 6.04GiB path /dev/sda7

Label: 'btrfs1'  uuid: 0f1c615f-30a0-4166-8a3c-987849551513
	Total devices 2 FS bytes used 233.54GiB
	devid    1 size 465.76GiB used 236.03GiB path /dev/sdc
	devid    2 size 298.09GiB used 236.03GiB path /dev/sdb

Comment 1 Fedora End Of Life 2015-11-04 14:58:40 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-12-02 04:34:34 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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