Red Hat Bugzilla – Bug 428346
RFE: clean up errors during ha lvm operations
Last modified: 2009-04-16 18:56:08 EDT
Description of problem:
I always seem to find some error in the log when doing different ha lvm operations.
This one is because a tag is missing on the volume group, but it's
supposed to be missing until this node becomes the server.
Jan 10 11:57:23 hayes-03 clurgmgrd: : <err> stop: Could not match
/dev/HAYES/ha3 with a real device
Not sure what this one is for.
Jan 10 11:58:07 hayes-02 clurgmgrd: <err> #60: Mangled reply from member
#1 during RG relocate
This one could an fyi or something other than a error.
Jan 10 11:58:33 hayes-01 clurgmgrd: : <err> startFilesystem: Creating
mount point /mnt/lvm3 for device /dev/mapper/HAYES-ha3
Version-Release number of selected component (if applicable):
These are in the fs.sh script, I believe and will require lon's input.
Lon, I believe the important point here is that upon initial startup; if an FS is on top of an logical volume:
1) the file system may not be mounted
2) the logical volume may not exist (until activation)
So, of course "<err> stop: Could not match /dev/HAYES/ha3 with a real device", but that doesn't mean it's
an error... especially if it is shutting down and not mounted.
Created attachment 291759 [details]
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
This was causing an erroneous fail-on-stop which shouldn't have been caused,
therefore, we should include in 5.2 with the rest of the LVM updates.
Marking lon's fixed verified.
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 the 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.