Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 661493 Details for
Bug 886109
[Intel F17 Bug] Failed disk is still available in volume/container
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
[patch]
udev rules patch
correct-65-md-incremental-rules-in-case-a-raid-disk-fails.patch (text/plain), 2.11 KB, created by
Maciej Patelczyk
on 2012-12-11 14:30:44 UTC
(
hide
)
Description:
udev rules patch
Filename:
MIME Type:
Creator:
Maciej Patelczyk
Created:
2012-12-11 14:30:44 UTC
Size:
2.11 KB
patch
obsolete
>Correct 65-md-incremental rules in case a raid disk fails. > >When we have a raid volume and one of disks fails, >the failed disk is still present in volume and container. >The raid volume is in normal state (but should be in degraded state) >and rebuild cannot start. > >If the disk fails and "$env{ID_PATH}" is null, udev runs >"/sbin/mdadm -If sdX --path" (what does nothing - it is an incorrect >mdadm's command), instead of "/sbin/mdadm -If sdX". > >This patch adds rules: if "$env{ID_PATH}" is null, run >"/sbin/mdadm -If sdX". > >Signed-off-by: Marcin Tomczak <marcin.tomczak@intel.com> > >diff --git a/65-md-incremental.rules b/65-md-incremental.rules >index 0045d99..3083dca 100644 >--- a/65-md-incremental.rules >+++ b/65-md-incremental.rules >@@ -26,8 +26,12 @@ ENV{DM_MULTIPATH_DEVICE_PATH}=="?*", GOTO="md_end" > # array members either) > SUBSYSTEM=="block", ACTION=="add", ENV{ID_FS_TYPE}=="linux_raid_member", \ > RUN+="/sbin/mdadm -I $env{DEVNAME}" >-SUBSYSTEM=="block", ACTION=="remove", ENV{ID_FS_TYPE}=="linux_raid_member", \ >+SUBSYSTEM=="block", ACTION=="remove", ENV{ID_PATH}=="?*", \ >+ ENV{ID_FS_TYPE}=="linux_raid_member", \ > RUN+="/sbin/mdadm -If $name --path $env{ID_PATH}" >+SUBSYSTEM=="block", ACTION=="remove", ENV{ID_PATH}!="?*", \ >+ ENV{ID_FS_TYPE}=="linux_raid_member", \ >+ RUN+="/sbin/mdadm -If $name" > > # Next, check to make sure the BIOS raid stuff wasn't turned off via cmdline > IMPORT{cmdline}="noiswmd" >@@ -36,8 +40,12 @@ ENV{noiswmd}=="?*", GOTO="md_imsm_inc_end" > ENV{nodmraid}=="?*", GOTO="md_imsm_inc_end" > SUBSYSTEM=="block", ACTION=="add", ENV{ID_FS_TYPE}=="isw_raid_member", \ > RUN+="/sbin/mdadm -I $env{DEVNAME}" >-SUBSYSTEM=="block", ACTION=="remove", ENV{ID_FS_TYPE}=="isw_raid_member", \ >+SUBSYSTEM=="block", ACTION=="remove", ENV{ID_PATH}=="?*", \ >+ ENV{ID_FS_TYPE}=="isw_raid_member", \ > RUN+="/sbin/mdadm -If $name --path $env{ID_PATH}" >+SUBSYSTEM=="block", ACTION=="remove", ENV{ID_PATH}!="?*", \ >+ ENV{ID_FS_TYPE}=="isw_raid_member", \ >+ RUN+="/sbin/mdadm -If $name" > LABEL="md_imsm_inc_end" > > # Next make sure that this isn't a dm device we should skip for some reason >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 886109
: 661493