Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1534904 - UDisks reports wrong thinpool size
UDisks reports wrong thinpool size
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: udisks2 (Show other bugs)
7.5
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Vojtech Trefny
Storage QE
:
Depends On:
Blocks: 1583658 1583663
  Show dependency treegraph
 
Reported: 2018-01-16 04:21 EST by Vojtech Trefny
Modified: 2018-06-13 05:09 EDT (History)
4 users (show)

See Also:
Fixed In Version: udisks2-2.7.3-5
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1583658 (view as bug list)
Environment:
Last Closed: 2018-04-10 11:43:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0868 None None None 2018-04-10 11:44 EDT

  None (edit)
Description Vojtech Trefny 2018-01-16 04:21:41 EST
UDisks reports size for thinpools to be double than it actually is.

$ busctl get-property org.freedesktop.UDisks2 /org/freedesktop/UDisks2/lvm/test/thinpool org.freedesktop.UDisks2.LogicalVolume Size
t 109051904

$ sudo lvs
  LV       VG                 Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert                                                
  thinpool test twi-a-tz-- 52.00m 

There is already a fix upstream -- https://github.com/storaged-project/udisks/commit/821bc20911e9a446b943cf40abe0e8a8132bf418
Comment 4 Bohdan Milar 2018-02-07 14:34:34 EST
Tested on x86_64, ppc64, ppc64le, aarch64.

Bug reproduced with udisks2-2.7.3-4.
NOT reproduced with udisks2-2.7.3-6.

Fix verified.
Comment 7 errata-xmlrpc 2018-04-10 11:43:20 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0868

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