How to obtain the size of repositories in Red Hat Satellite

Environment

• Red Hat Satellite 6.x up to the 6.9 release.

Issue

• When trying to export repositories in Satellite 6 the /var/cache/pulp filesystem is filling up and the task fails.
• Current /var/cache/pulp volume is not sized properly.
• Need to calculate how much storage space a Content View is currently taking on the filesystem.

Resolution

• Note If the download policy for a particular product is set to on-demand, the size you will get for this particular product under this procedure will only reflect the size of the already downloaded packages for this product.

• Check how much storage space each Content View takes:

    # cd /var/lib/pulp/published/yum/https/repos/<ORG NAME>/content_views
    # du -Lsh * 2>/dev/null | sort -h
  

• Check how much storage space each lifecycle environment takes:

    # cd /var/lib/pulp/published/yum/https/repos/<ORG NAME>/<LIFECYCLE ENVIRONMENT>
    # du -Lsh * 2>/dev/null
  

• For example, displaying how much space all Content Views in the Production Lifecycle Environment take:

    # cd /var/lib/pulp/published/yum/https/repos/MyOrganization/Production
    # du -Lsh 2>/dev/null
    35G      .
  

NOTE: For content exporting purposes, if you plan to export the whole life cycle environment, your /var/cache/pulp file system should be at least the size of the largest Content View in the particular Lifecycle environment you plan to export.

For more KB articles/solutions related to Red Hat Satellite 6.x Pulp 2.0 Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Pulp 2.0-related Issues

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.