RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Persistent data package now provides over 10 binaries (cache, thin, era) each with noticeable size (C++ code...). Probably a lot of code is shared among them so a more space-efficient way should be used here to reduce the disk space requirements - since those tools are going to be needed in initramdisk.

In general we may probably use a single binary and provide multiple command line interfaces (like lvm2 does) - use use a share library for common part and build separate commands.


Version-Release number of selected component (if applicable):
device-mapper-persistent-data  0.3.2-1

How reproducible:


Steps to Reproduce:
1. size of device-mapper-persistent-data package it too large.

Actual results:


Expected results:
Significantly reduced size of package and installed files.

Additional info:

Appears to be addressed upstream: https://github.com/jthornber/thin-provisioning-tools/issues/8

Verified on device-mapper-persistent-data-0.5.6-1.el6.

Installed Packages
Name        : device-mapper-persistent-data
Arch        : x86_64
Version     : 0.5.6
Release     : 1.el6
Size        : 1.0 M

###########
device-mapper-persistent-data-0.3.2-1.el6

Installed Packages
Name        : device-mapper-persistent-data
Arch        : x86_64
Version     : 0.3.2
Release     : 1.el6
Size        : 16 M

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://rhn.redhat.com/errata/RHBA-2016-0960.html