RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Following on from bug 1154782 there was some discussion about the default size and number of resource groups chosen, and the factors which should be taken into account when choosing them. The key point was that it's more important to optimise for a large number of rgrps per node than only taking the device size into account. We should be able to make better decisions for smaller file systems if we take the number of journals to indicate the number of nodes.

Where possible, #rgrps should be at least 10x #journals. This should be increased slightly to pre-empt journals being added subsequently.

We should make sure that these factors are mentioned in manpages so that users will know that choosing a number of journals well at mkfs time may give better results than relying on gfs2_jadd later.

I'm closing this as a duplicate of bug 1498068 as the work that set the default size of the journals conditionally essentially enforced a minimum proportion of journal space for small filesystems (maximising the space used by resource groups). See 04598c779cb1309f342ca14b555df5eb676e38c9

*** This bug has been marked as a duplicate of bug 1498068 ***