Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 723638

Summary: Backport upstream extensions for lsblk
Product: Red Hat Enterprise Linux 6 Reporter: Milan Broz <mbroz>
Component: util-linux-ngAssignee: Karel Zak <kzak>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 6.1CC: agk, azelinka, jmarko, pvrabec
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 17:11:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Milan Broz 2011-07-20 18:06:01 UTC
Description of problem:

lsblk utility is useful for storage performance tunning and block device diagnostics (it is standard part of RHEL6 sosreport now).

For enterprise multipath devices is important not only check io scheduler parameters for mpath device itself but also for the underlying devices. 

There are new lsblk flags in upstream which allows trivial system observation and problem detection - namely reporting of device state (running, offline, suspended etc.), io scheduler and queue size.

e.g.
# ./lsblk -t -o name,state,type,phy-sec,log-sec,sched,rq-size /dev/sd[if]
NAME            STATE   TYPE  PHY-SEC LOG-SEC SCHED RQ-SIZE
sdf             running disk      512     512 cfq       128
└─mpatha (dm-0) running mpath     512     512 cfq       128
sdi             running disk      512     512 cfq       128
└─mpatha (dm-0) running mpath     512     512 cfq       128

# ./lsblk -t /dev/sd[if]
NAME            ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE
sdf                     0    512      0     512     512    1 cfq       128
└─mpatha (dm-0)         0    512      0     512     512    1 cfq       128
sdi                     0    512      0     512     512    1 cfq       128
└─mpatha (dm-0)         0    512      0     512     512    1 cfq       128

If possible, please backport these options to RHEL6.2

Version-Release number of selected component (if applicable):
util-linux-ng-2.17.2-12.el6

Comment 8 errata-xmlrpc 2011-12-06 17:11:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2011-1691.html