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.
A note on the benefit of using XFS as the file system in a Satellite 6 environment must be added to the "Storage Recommendations" section of
"2.1. Storage Requirements and Recommendations" in the Installation Guide.
See the following comments from the Satellite 6 mailing list for the details -
Sean O'Keeffe -
"I would recommend XFS for el6 & el7, XFS doesn't have an inode limit like EXT4 you can also increase the number of inodes on XFS using xfs_grow. As Satellite uses a lot of symlinks it's likely that you'll run out of inodes if using ext4 and the default number of inodes."