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.
Customers are installing satelite with slow IO which is causing a negative experience. The install guide, in an pre-requisite sections, should call out the importance of fast IO. Ideally, it is near the suggestion to use XFS.
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
Recommended minimum:
We recommend a minimum of 80MB/sec Buffered Read Time for read access to the disk used in the /var/ partition. Numbers lower than this on average can cause extreme performance issues with your Satellite installation, upgrade and day to day operations.
In extreme situations slow IO (in the order of 10-20 megabytes/second speeds) to the /var partition has caused Satellite 6.1 to 6.2 upgrades to take in excess of 24 hours or more.
Testing via the "hdparm -tT" command and examining the "Timing buffered disk reads" line can give a quick estimation on the read speeds for your disk and can quickly spot a potential problem.