NetBSD Problem Report #9715
Received: (qmail 667 invoked from network); 3 Jun 1999 03:44:49 -0000
Message-Id: <199904290342.UAA08830@tel-aran-rhiod.flame.org>
Date: Wed, 28 Apr 1999 20:42:23 -0700 (PDT)
From: Michael Graff <explorer@flame.org>
Reply-To: explorer@flame.org
To: gnats-bugs@gnats.netbsd.org
Subject: raidctl should explain that clean: 0 means not, clean: 1 means it is.
X-Send-Pr-Version: 3.95
>Number: 9715
>Category: bin
>Synopsis: raidctl should explain that clean: 0 means not, clean: 1 means it is.
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: bin-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Mar 31 07:30:16 +0000 2000
>Closed-Date: Mon Apr 10 17:09:08 +0000 2000
>Last-Modified: Mon Apr 10 17:09:08 +0000 2000
>Originator: Michael Graff
>Release: 1.4_BETA
>Organization:
flame.org: yes, we do know everything
>Environment:
System: NetBSD tel-aran-rhiod.flame.org 1.4_ALPHA NetBSD 1.4_ALPHA (FLAME_HOME) #0: Sat Apr 17 16:36:46 PDT 1999 explorer@tel-aran-rhiod.flame.org:/u1/OS/NetBSD/src/sys/arch/i386/compile/FLAME_HOME i386
>Description:
It would be much nicer if raidctl, and the man page, would explain what
the state of the clean bit means. Of course, it would also be nice if
raidctl -s raid0
displayed the overall state of each component, rather than having to walk
through them manually...
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed
State-Changed-By: oster
State-Changed-When: Mon Apr 10 10:08:16 PDT 2000
State-Changed-Why:
This is a duplicate of bin/7695 (which is already fixed).
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.