>Number:         30074
>Category:       misc
>Synopsis:       proposed changes to RAIDframe related rc.d scripts
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    misc-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 27 18:12:00 +0000 2005
>Originator:     Jukka Salmi
>Release:        NetBSD 3.99.3
>Environment:
$ ident /etc/rc.d/raidframe*
/etc/rc.d/raidframe:
      $NetBSD: raidframe,v 1.9 2004/08/13 18:08:03 mycroft Exp $
/etc/rc.d/raidframeparity:
      $NetBSD: raidframeparity,v 1.3 2004/10/11 15:00:51 christos Exp $
System: NetBSD moray.salmi.ch 3.99.3 NetBSD 3.99.3 (GENERIC.NOEHCI.APM) #0: Tue Apr 26 18:54:44 CEST 2005 build@moray.salmi.ch:/build/nbsd/i386/sys/arch/i386/compile/GENERIC.NOEHCI.APM i386
Architecture: i386
Machine: i386
>Description:

On a current NetBSD system using RAIDframe and default rc.d scripts,
parity checking the RAID set is done late in the boot process and in
the background: until it succeeds the data is not protected against a
component failure.

Although this may be desired behaviour for some people, I'd appreciate
the possibility to choose whether parity checking should be done as early
as possible (i.e. before fsck runs and filesystems are mounted) and in the
foreground, or as it is right now (late and in the background).

I proposed the changes needed to do this to current-users on 2005/04/22:
http://mail-index.netbsd.org/current-users/2005/04/22/0017.html - I interpret
the lack of replies as "no objections" ;-)
 
The patch (see Fix: below) adds this functionality: setting
raidframeparity_early to NO (the default) doesn't change any behaviour;
setting it to YES runs the parity check right after non-auto-configured
RAID sets are configured and in the foreground.

>How-To-Repeat:
n/a
>Fix:
I'll append the patch to this PR ASAP; additionally, it's available from
http://salmi.ch/~jukka/RAIDframe-parity_rc.d.patch