You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: 66426469d0

master

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

001

002

003

004

005

006

007

008

009

010

011

012

013

014

015

016

017

018

019

020

021

022

023

024

025

026

027

028

029

030

031

032

033

033-502

034

035

036

037

038

039

040

041

042

043

044

045

046

047

048

049

050

051

052

053

054

055

056

RHEL-7.1

RHEL-7.2

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '66426469d0'

${ noResults }

dracut/modules.d/90mdraid

History

Michal Soltys 66426469d0 90mdraid: fix/adjust force-run script ... 1) mdadm -As --auto=yes --run 2>&1 | vinfo (removed) Currently such auto assembly will not complete or force-run partially assembled arrays. It might assemble "concurrent" separate array and force-run it, if possible (though the chances of suddenly showing missing components in this scenario - a script run after udev timeout - are pretty thin). See [1] for details. Also see #3 below. 2) mdadm -Is --run 2>&1 (removed) This will only force-run native arrays - arrays in containers will not be affected. See [1] for details. Also see #3 below. 3) mdadm -R run loop (implicitly handles #1 & #2) This loop does everywthing that #1 & #2 are expected to do. Thus, the above invocations are simply redundant and this is the most safe and flexible option. Also, it shouldn't be necessary to go under md/ directory, as those are just symlinks to /dev/md[0-9]*. Certain checks were changed to strict ones (array state, degraded state) instead of relying on env tricks. 'cat' was added explicitly to installed programs (it has been used implicitly in shutdown script either way) 4) mdmon bug See [1] for details as well. In short - force-run arrays in containers will not have mdmon started, so we do that manually. 5) stop/run queue magic Also removed. mdadm -R will only cause change events to the array itself, and they should not be an issue. [1] http://article.gmane.org/gmane.linux.raid/35133 Signed-off-by: Michal Soltys <soltys@ziu.info>		14 years ago
..
65-md-incremental-imsm.rules	90mdraid: containers are not runnable	14 years ago
md-noimsm.sh	…
md-shutdown.sh	…
md_finished.sh	90mdraid: containers are not runnable	14 years ago
mdadm_auto.sh	…
mdmon-pre-udev.sh	…
mdraid-cleanup.sh	90mdraid: fix/adjust mdraid-cleanup	14 years ago
mdraid_start.sh	90mdraid: fix/adjust force-run script	14 years ago
module-setup.sh	90mdraid: fix/adjust force-run script	14 years ago
parse-md.sh	90mdraid: fix/adjust force-run script	14 years ago