Bug 1393160

Summary: isw dmraid raid1 can't be activated after reboot
Product: Red Hat Enterprise Linux 6 Reporter: Zhang Xiaotian <xiaotzha>
Component: dmraidAssignee: Heinz Mauelshagen <heinzm>
Status: CLOSED WONTFIX QA Contact: Zhang Yi <yizhan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.8CC: agk, heinzm, jbrassow, 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:
: 1393627 (view as bug list) Environment:
Last Closed: 2017-12-06 11:19:03 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:
Bug Depends On:    
Bug Blocks: 1393627    

Description Zhang Xiaotian 2016-11-09 02:20:20 UTC
Description of problem:
 After the reboot, isw dmraid raid1 can't be activated

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 # dmraid  -f  isw -C Raid1 --type 1 --disk "/dev/sdb /dev/sdc"


     Create a RAID set with ISW metadata format     

RAID name:      Raid1
RAID type:      RAID1
RAID size:      111G (234432094 blocks)
DISKS:     /dev/sdb, /dev/sdc, 


About to create a RAID set with the above settings. Continue ? [y/n] :y

# dmraid -s
*** Group superset isw_ceggiagge
--> Subset
name   : isw_ceggiagge_Raid1
size   : 234432000
stride : 128
type   : mirror
status : ok
subsets: 0
devs   : 2
spares : 0
[root@dhcp-12-134 Desktop]# dmraid -r
/dev/sdc: isw, "isw_ceggiagge", GROUP, ok, 234441646 sectors, data@ 0
/dev/sdb: isw, "isw_ceggiagge", GROUP, ok, 234441646 sectors, data@ 0

# dmraid -tay
isw_ceggiagge_Raid1: 0 234432000 mirror core 2 131072 nosync 2 /dev/sdb 0 /dev/sdc 0 1 handle_errors

========  reboot =============

# dmraid -s
*** Group superset isw_ceggiagge
--> Subset
name   : isw_ceggiagge_Raid1
size   : 234432000
stride : 128
type   : mirror
status : ok
subsets: 0
devs   : 2
spares : 0

# dmraid -ay
RAID set "isw_ceggiagge_Raid1" was not activated
ERROR: device "isw_ceggiagge_Raid1" could not be found

# dmraid -r
/dev/sdc: isw, "isw_ceggiagge", GROUP, ok, 234441646 sectors, data@ 0
/dev/sdb: isw, "isw_ceggiagge", GROUP, ok, 234441646 sectors, data@ 0

# dmraid -ay
RAID set "isw_ceggiagge_Raid1" was not activated
ERROR: device "isw_ceggiagge_Raid1" could not be found


Actual results:


Expected results:
dmraid -ay was activated

Additional info:

Comment 1 Zhang Xiaotian 2016-11-10 02:28:16 UTC
I alse encountered this issue on RHEL7.3 with kernel-3.10.0-514.el7,but it prompt that device-mapper target type "raid45" is not in the kernel.

# dmraid -s
*** Group superset isw_degjjibgb
--> Subset
name   : isw_degjjibgb_Raid5
size   : 3907031296
stride : 128
type   : raid5_la
status : ok
subsets: 0
devs   : 3
spares : 0

# dmraid -ay
ERROR: device-mapper target type "raid45" is not in the kernel
RAID set "isw_degjjibgb_Raid5" was not activated
ERROR: device "isw_degjjibgb_Raid5" could not be found

# dmraid -tay
isw_degjjibgb_Raid5: 0 3907031296 raid45 core 2 131072 nosync raid5_la 1 128 3 -1 /dev/sdd 0 /dev/sdc 0 /dev/sdb 0

Comment 2 Jan Kurik 2017-12-06 11:19:03 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/