Red Hat Bugzilla – Bug 433183
SOS does not collect ext3 filesystem information.
Last modified: 2013-07-28 20:44:41 EDT
Description of problem:
SOS(sosreport) does not collect Ext2/3 filesystems information.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Execute sysreport(sos) on RHEL4/RHEL5
Not collects ext3 filesystem information.
should include the output of the command: "dumpe2fs <ext2 filesystem>"
Please see the attached file.
Created attachment 295092 [details]
Comment on attachment 295092 [details]
### This program is free software; you can redistribute it and/or modify
## it under the terms of the GNU General Public License as published by
## the Free Software Foundation; either version 2 of the License, or
## (at your option) any later version.
## This program is distributed in the hope that it will be useful,
## but WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
## GNU General Public License for more details.
## You should have received a copy of the GNU General Public License
## along with this program; if not, write to the Free Software
## Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
"""dumpe2fs related information
inpipe, pipe = os.popen4("mount -t ext3", 'r')
for line in pipe.readlines():
L = string.split(line)
str = "dumpe2fs " + L
Thanks for the patch, however, all this needed was a minor alteration to the
filesys plugin as it was already capturing ext2/3 tunable parameters. dumpe2fs
just extends on that so tune2fs was replaced.
Committed to filesys plugin
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
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.