Red Hat Bugzilla – Bug 503530
gfs2_edit produces unaligned access
Last modified: 2010-03-30 04:53:59 EDT
Description of problem:
gfs2_edit(20731): unaligned access to 0x600000000005b2ee, ip=0x400000000004d160
Version-Release number of selected component (if applicable):
gfs2_edit savemeta /dev/sdc1 metadata
Steps to Reproduce:
1. mkfs.gfs2 -t a3cluster:a3gfs2 -p lock_nolock -j 2 -J 8 /dev/sdc1
2. gfs2_edit savemeta /dev/sdc1 metadata
metadata saved, unaligned access reported
metadata saved, no unaligned access messages
restoring metadata produces couple of more unaligned accesses:
gfs2_edit(20750): unaligned access to 0x600000000005902e, ip=0x400000000004d160
gfs2_edit(20750): unaligned access to 0x6000000000059046, ip=0x400000000004d5a0
gfs2_edit(20750): unaligned access to 0x600000000005904e, ip=0x400000000004d5f0
gfs2_edit(20750): unaligned access to 0x600000000005905a, ip=0x400000000004ce61
gfs2_edit(20750): unaligned access to 0x6000000000059062, ip=0x400000000004ceb0
# gfs2_edit -p rg 0 /dev/sdc1
gfs2_edit(23882): unaligned access to 0x60000fffffdc755c, ip=0x400000000004e151
gfs2_edit(23882): unaligned access to 0x60000fffffdc756c, ip=0x400000000004e1f0
I'm sure we can fix this; setting devel_ack.
Created attachment 354204 [details]
Patch to fix the problem
This patch fixes the savemeta, restoremeta and rgrp print problems
with unaligned access.
The patch was pushed to the master branch of the gfs2-utils git
tree, and the RHEL5, STABLE2 and STABLE3 branches of the cluster
git tree for inclusion into 5.5. Changing status to Modified.
The RHEL5 version was tested on link-13 and the upstream version
was tested on system "kool".
Pushed to the RHEL55 branch of cluster.git. Changing status to POST.
Built according to the new procedure. Changing to Modified.
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.