Red Hat Bugzilla – Bug 459630
GFS2: changes needed to gfs2-utils due to gfs2meta fs changes in bz 457798
Last modified: 2010-01-11 22:41:18 EST
Description of problem:
Bug #457798 changed the metadata file system from the metafs type
to having a new -o meta mount option. Three of the user space GFS2
programs need to be changed to match the new value. Those are:
mkfs.gfs2 (gfs2_jadd, gfs2_grow), gfs2_quota and gfs2_tool.
They all use the libgfs2 function find_gfs2_meta, which is what needs
to be changed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. gfs2_jadd ... /mnt/gfs2
2. gfs2_tool lockdump /mnt/gfs2
Will fail with the fix for bug 457798.
All of these tools should work perfectly.
This fix is co-dependent with bug #457798 and their respective
fixes should be shipped at the same time. The kernel doesn't break
without this fix, but the GFS2 userland tools may not work properly.
Any fix done for this bugzilla will, however, require that fix in
Created attachment 315223 [details]
patch to mount '-o meta' insteaed of '-t gfs2meta'
This patch makes the user tools now look for a gfs2 filesystem with -o meta mount option, instead of looking for a 'gfs2meta' filesystem. Also, when mounting, we mount '-t gfs2 -o meta' instead of '-t gfs2meta'
Created attachment 316527 [details]
One-liner to use gfs2 path instead of gfs2 device to mount metafs
The changes to the gfs2meta component of gfs2 (through bz 457798) does not require any major changes to gfs2_utils except this one liner. We now use the gfs2 mount point rather than the device to mount the meta fs.
Checking in this patch to RHEL5, STABLE2.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.