Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause:
Previous versions of gfs2_edit saved GFS2 metadata uncompressed.
Consequence:
Saved GFS2 metadata sets could take up a lot of storage space and transferring them (e.g. for support and debugging) would be slow.
Change:
gzip compression was added to the metadata saving and restoring functions of gfs2_edit.
Result:
GFS2 metadata sets are now compressed when saving and decompressed when restoring. The user can specify the compression level with a command line option.
+++ This bug was initially created as a clone of Bug #695767 +++
(Bob's idea)
1) "gfs2_edit savemeta" should compress metadata.
2) "gfs2_edit restoremeta" should decompress the metadata if it recognises the file as being compressed
Things to decide:
a) Preference of bzip2, gzip, or other for compression?
b) --nozip flag to turn off the feature and just save the metadata as before?
--- Additional comment from anprice on 2011-04-13 09:23:23 EDT ---
Created attachment 491757[details]
First attempt
Attaching a first attempt patch. The usually restoremeta warnings apply.
--- Additional comment from anprice on 2011-04-14 12:29:24 EDT ---
Created attachment 492167[details]
Second attempt
This patch adds a -nocompress option, abstracts away the calls to write/gzwrite, and adds more documentation. It also uses compression level 5 instead of the default 6 as it seems to speed up the compression significantly with very little effect on the compressed file size (for my small test cases at least).
--- Additional comment from anprice on 2011-05-04 14:02:14 EDT ---
Created attachment 496861[details]
Third attempt
This revision of the patch replaces the -nocompress option with the -z <0-9> option and removes the unnecessary strdup() mentioned on the mailing list.
--- Additional comment from anprice on 2011-05-05 05:50:20 EDT ---
Third patch is now in gfs2_utils.git master
Created attachment 504874[details]
Additional patch for RHEL6
Further testing threw up a problem with the older zlib version in RHEL6. This additional patch makes my tests pass and is now in the RHEL6 branch of cluster.git, so setting back to POST.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause:
Previous versions of gfs2_edit saved GFS2 metadata uncompressed.
Consequence:
Saved GFS2 metadata sets could take up a lot of storage space and transferring them (e.g. for support and debugging) would be slow.
Change:
gzip compression was added to the metadata saving and restoring functions of gfs2_edit.
Result:
GFS2 metadata sets are now compressed when saving and decompressed when restoring. The user can specify the compression level with a command line option.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1516.html