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 1393250

Summary: Mislead error message when executing command of dmraid -ay
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:13:15 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:
Embargoed:

Description Zhang Xiaotian 2016-11-09 08:06:16 UTC 
Description of problem:
Mislead error message when executing command of dmraid -ay

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.It occurs every time when executing command of dmraid -ay

Steps to Reproduce:
1.Create RAID1 with command of dmraid
2.#dmraid -ay
  RAID set "isw_bijaajcjdc_Raid1" was activated
  device "isw_bijaajcjdc_Raid1" is now registered with dmeventd for monitoring

  #dmraid -s
  *** Group superset isw_bijaajcjdc
   --> Active Subset
   name   : isw_bijaajcjdc_Raid1
   size   : 1953515520
   stride : 128
   type   : mirror
   status : ok
   subsets: 0
   devs   : 2
   spares : 0


3.cat /var/log/message

Nov  9 02:01:39 dhcp-12-134 dmeventd[4563]: SGPIO handling enabled
Nov  9 02:01:39 dhcp-12-134 dmeventd[4563]: _get_device_info: : device not found.
Nov  9 02:01:39 dhcp-12-134 dmeventd[4563]: ERROR: UUID "DMRAID-isw_bijaajcjdc_Raid1" is already registered
Nov  9 02:01:39 dhcp-12-134 dmeventd[4563]: Failed to register device 
isw_bijaajcjdc_Raid1.


Actual results:
Show error message with raid1 was activated

Expected results:
NO error message with raid1 was activated

Additional info:
Comment 1 Zhang Xiaotian 2016-11-09 08:17:43 UTC 
I also encountered this issue on RAID5,at the same time,it also shows some other information.

#cat /var/log/message
Nov  9 03:11:36 dhcp-12-134 kernel: device-mapper: dm-raid45: initialized v0.2597k
Nov  9 03:11:36 dhcp-12-134 kernel: device-mapper: dm-raid45: rs->set.sectors_per_dev=1953515648
Nov  9 03:11:36 dhcp-12-134 kernel: device-mapper: dm-raid45: HM stripes=1/size=256 min=35 xor_blocks=45 hm=50 max=50
Nov  9 03:11:36 dhcp-12-134 kernel: device-mapper: dm-raid45: /dev/sdb is raid disk 0
Nov  9 03:11:36 dhcp-12-134 kernel: device-mapper: dm-raid45: /dev/sdc is raid disk 1
Nov  9 03:11:36 dhcp-12-134 kernel: device-mapper: dm-raid45: /dev/sdd is raid disk 2
Nov  9 03:11:36 dhcp-12-134 kernel: device-mapper: dm-raid45: 128/128/256 sectors chunk/io/recovery size, 80 stripes
Nov  9 03:11:36 dhcp-12-134 kernel: algorithm "xor_16", 3 chunks with 2500MB/s
Nov  9 03:11:36 dhcp-12-134 kernel: RAID5 (left asymmetric) set with net 2/3 devices
Nov  9 03:11:36 dhcp-12-134 kernel: device-mapper: table: 253:3: adding target device (start sect 0 len 3907031296) caused an alignment inconsistency
Nov  9 03:11:36 dhcp-12-134 kernel: device-mapper: dm-raid45: raid_resume...
Nov  9 03:11:37 dhcp-12-134 dmeventd[7925]: SGPIO handling enabled
Nov  9 03:11:37 dhcp-12-134 dmeventd[7925]: _get_device_info: : device not found.
Nov  9 03:11:37 dhcp-12-134 dmeventd[7925]: _get_device_info: : device not found.
Nov  9 03:11:37 dhcp-12-134 dmeventd[7925]: ERROR: UUID "DMRAID-isw_degjjibgb_Raid5" is already registered
Nov  9 03:11:37 dhcp-12-134 dmeventd[7925]: Failed to register device isw_degjjibgb_Raid5.
Comment 2 Jan Kurik 2017-12-06 12:13:15 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/