Bug 543862

Description of problem:

According to Installation Guide section 2.2.1. x86 and x86_64 Hardware Requirements, 
Recommended: "5 GB storage for base install of Red Hat Enterprise Linux"

which one can assume means a 5 GB "/" partition

I made mine 10 GB, but still ran into space problems as over time /var/cache/rhn fills up

How reproducible:

Every time

Steps to Reproduce:
1. Install RHEL with 5 GB "/" partition
2. Install RHN Satellite and import 3 or more channels (I used rhel-x86_64-server-5, rhel-i386-server-5, rhel-x86_64-as-4, rhel-i386-as-4)
3. Export all channels 
  
Actual results:

"/" fills up


Additional info:

With the above 4 channels synced and exported, /var/cache/rhn uses 6.6 GB of space.

I would suggest modifying/expanding the documentation as follows:
a) increase the recommended storage space for "/" or have an explicit mention of a size recommendation for /var/cache/ or /var/cache/rhn
b) Provide guidelines on maintenance of the content of this directory e.g. 
i) manually remove (rm) or purge/prune using one of the provided cmd-line tools
ii) whether it should to be backed up or not. Is it recreated from existing content internal to the Satellite or downloaded from RHN Hosted when required (which customers with minimal bandwidth will want to avoid)

Older version of the RHN Documentation mentioned maintenance of this directory, e.g.
http://www.redhat.com/docs/manuals/RHNetwork/satellite/3.6/cache-issues.html


+++ This bug was initially created as a clone of Bug #218875 +++

Description of problem:
The release notes for RHN Satellite 5 beta say that the / file system should be
at least 3GB.  I made mine 4GB.  4GB is insufficient for downloading the
metadata for all RHEL{3,4,5} channels - /var/cache/rhn fills up.  Please
increase the recommended space for / to something that'll work.

--- Additional comment from matt_domsch on 2008-10-29 10:21:53 EDT ---

These have been open for years with no investigation or resolution.  Since then the code base has moved on significantly, such that many of these no longer would apply to the current spacewalk code.  I'm closing these requests in the hope they're no longer necessary, or if they are, they'll get discovered anew.