Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionStephen Wadeley
2016-04-25 20:00:40 UTC
Description of problem:
The guides mention the need to allow space when making backups or exporting repos, but I have not found a way to easily determine the on-disk size of a repo.
Such a tool would be appreciated.
Additional info:
One way to do this would be to add a no-op option to the `hammer repository export` command which tells you the space that would be required.
Another way would be if the `hammer repo list` could provide that info. Whether the info is calculated on the fly or read from a value updated at repo sync time should not matter to the user.
As hammer commands get info from the API I will file this bug against the API component.
Thank you