Bug 1393286

Summary: It takes too long time to execute dmraid -an on raid5
Product: Red Hat Enterprise Linux 6 Reporter: Zhang Xiaotian <xiaotzha>
Component: dmraidAssignee: Heinz Mauelshagen <heinzm>
Status: CLOSED WONTFIX QA Contact: Zhang Xiaotian <xiaotzha>
Severity: high Docs Contact:
Priority: high    
Version: 6.8CC: agk, heinzm, msnitzer, prajnoha, yizhan, zkabelac
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 12:27:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Zhang Xiaotian 2016-11-09 09:29:34 UTC 
Description of problem:
It takes too long time to execute dmraid -an on raid5.Under the same environments,this issue doesn't appear on raid1.

Version-Release number of selected component (if applicable):
RHEL6.8 with kernel-2.6.32-642.el6.x86_64

# rpm -qa dmraid*
dmraid-events-1.0.0.rc16-11.el6.x86_64
dmraid-1.0.0.rc16-11.el6.x86_64

How reproducible:
Always.

Steps to Reproduce:
1.create a isw dmraid raid5
2. # dmraid -ay
  RAID set "isw_degjjibgb_Raid5" was activated
  device "isw_degjjibgb_Raid5" is now registered with dmeventd for monitoring

3.# dmraid -an
  ERROR: device "isw_degjjibgb_Raid5" is not currently being monitored
  === **** cursor isn't return *****=====

Actual results:
no ends of last than 2 hours

Expected results:
it ends soon

Additional info:
#ps -aux
root   8436  0.6  0.0  26288  1360 pts/0    D+   03:22   0:21 dmraid -an
Comment 1 Jan Kurik 2017-12-06 12:27:52 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/