NetBSD Problem Report #8588

Received: (qmail 8624 invoked from network); 8 Oct 1999 20:08:10 -0000
Message-Id: <>
Date: Fri, 8 Oct 1999 16:08:11 -0400 (EDT)
Subject: raidframe diagnostics suck
X-Send-Pr-Version: 3.95

>Number:         8588
>Category:       kern
>Synopsis:       raidframe diagnostics suck
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    oster
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Oct 09 09:24:00 +0000 1999
>Last-Modified:  Sun Oct 31 18:15:59 +0000 1999
>Release:        1.4.1
	Basis Technology/Red Bean Software/Gratuitous Organization for Gratuitous Software Enhancement
System: NetBSD ichi 1.4.1 NetBSD 1.4.1 (ICHI) #1: Fri Oct 8 14:54:48 EDT 1999 nemo@ichi:/usr/src/sys/arch/i386/compile/ICHI i386

I had a config file which raidctl was attempting to read to specify
which partitions a raid level 1 device was using.  Unfortunately,
I copied the example from the manpage, and failed to change the total
of 3 disks to 2.

The errors I saw were bizarre ioctl failures (no such device, I believe),
and these messages which I was able to see using dmesg:

RAIDFRAME: failed rf_ConfigureDisks with 2
RAIDFRAME: protectedSectors is 64
raidlookup on device: START layout failed!
Closing vnode for row: 0 col: 0
Closing vnode for row: 0 col: 1
Closing vnode for row: 0 col: 2
vnode was NULL
RAIDFRAME: failed rf_ConfigureDisks with 2

raidctl can certainly have better error checking, such that when obviously
bogus config files are passed to it, it complains.
see above
Responsible-Changed-From-To: kern-bug-people->oster 
Responsible-Changed-By: hwr 
Responsible-Changed-When: Sun Oct 31 10:13:06 PST 1999 
This is Greg's baby 

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.