Red Hat Bugzilla – Bug 506629
GFS2: gfs2_convert, parameter not understood on ppc
Last modified: 2010-01-11 22:43:57 EST
Description of problem:
Our test case attempted:
gfs2_convert -vy /dev/wic/wic0
<gfs2_convert usage message>
Parameter not understood: ÿ
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. gfs2_convert -vy /dev/wic/wic0 (on a ppc system)
Easy one-line fix (change variable from type char to int).
Requesting ack flags and a management decision on what release
to fix it.
Created attachment 349445 [details]
Patch to fix the problem
This is the patch that should fix the problem. I pushed this
patch upstream to the master branch of the gfs2-utils git tree
and the STABLE3, STABLE3, RHEL5 and RHEL54 branches of the
cluster git tree for inclusion into 5.4.
Fixed in RHEL5.4-Server-20090722.0 with gfs2-utils-0.1.61-1.el5.
Closing the bug as VERIFIED.
log from console:
[root@ibm-js12-03 ~]# gfs2_convert -vy /dev/sda3
gfs2_convert version 2 (built Jul 14 2009 12:54:25)
Copyright (C) Red Hat, Inc. 2004-2006 All rights reserved.
Examining file system
This program will convert a gfs1 filesystem to a gfs2 filesystem.
WARNING: This can't be undone. It is strongly advised that you:
1. Back up your entire filesystem first.
2. Run gfs_fsck first to ensure filesystem integrity.
3. Make sure the filesystem is NOT mounted from any node.
4. Make sure you have the latest software versions.
Converting resource groups.
6 inodes from 78 rgs converted.
Fixing file and directory information.
1 directories, 2 dirents fixed.
Converting journal space to rg space.
Addr 269a80 comes after rg at addr 259d19
Writing journal #1...done.
Building GFS2 file system structures.
Removing obsolete GFS1 file system structures.
Committing changes to disk.
/dev/sda3: filesystem converted successfully to gfs2.
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.