Description of problem: There is no support in the RHEL4 sosreport for gathering an lvmdump tarball that is used to debug LVM2 and device-mapper related problems. This is a standard format for this data that is supported/maintained by the upstream project via the lvmdump script that is installed with the lvm2 RPM (introduced in RHEL-4.5). Not having this data in the sosreport archive generates needless back/fore requests for additional info in dealing with LVM2/device-mapper problems. Version-Release number of selected component (if applicable): sos-1.7-6.1 How reproducible: 100% Steps to Reproduce: 1. make sure sos is installed 2. grep -r /usr/lib/python2.3/site-packages/sos Actual results: $ grep -r /usr/lib/python2.3/site-packages/sos $ Expected results: $ grep -r lvmdump /usr/lib/python2.3/site-packages/sos/plugins/devicemapper.py optionList = [("lvmdump", 'collect raw metadata from PVs', 'slow', False)] def do_lvmdump(self): sosGetCommandOutput("lvmdump -d %s" % os.path.join(self.cInfo['dstroot'],"lvmdump")) if self.getOption('lvmdump'): self.do_lvmdump() [...] Additional info:
There's also a bug in the upstream sos version now in RHEL5 - lvmdump should be run by default instead of the hard-coded lvm data gathering that now exists.
Unfortunately this bugzilla was not resolved in time for RHEL 4.7 Beta. It has now been proposed for inclusion in RHEL 4.8 but must regain Product Management approval.
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. http://rhn.redhat.com/errata/RHBA-2008-0663.html