From owner-cvs-src@FreeBSD.ORG  Fri Nov 18 10:19:45 2005
Return-Path: <owner-cvs-src@FreeBSD.ORG>
X-Original-To: cvs-src@FreeBSD.org
Delivered-To: cvs-src@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0171416A41F;
	Fri, 18 Nov 2005 10:19:45 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 584FF43D5D;
	Fri, 18 Nov 2005 10:19:43 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.48.2])
	by phk.freebsd.dk (Postfix) with ESMTP id C8643BC66;
	Fri, 18 Nov 2005 10:19:39 +0000 (UTC)
To: Scott Long <scottl@samsco.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 18 Nov 2005 01:46:34 MST."
	<437D94EA.90909@samsco.org> 
Date: Fri, 18 Nov 2005 11:19:38 +0100
Message-ID: <7052.1132309178@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Cc: John Polstra <jdp@FreeBSD.org>, cvs-src@FreeBSD.org,
	src-committers@FreeBSD.org, cvs-all@FreeBSD.org,
	Lukas Ertl <le@FreeBSD.org>
Subject: Re: cvs commit: src/sys/cam/scsi scsi_cd.c scsi_da.c src/sys/geom
	geom_disk.c geom_disk.h geom_subr.c 
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2005 10:19:45 -0000

In message <437D94EA.90909@samsco.org>, Scott Long writes:
>Lukas Ertl wrote:

>What does this mean for other drivers?  RAID arrays can come and go
>at runtime, either due to drive failure or due to actions by the user
>via a management app.  I don't recall ever seeing a problem like this
>with the aac driver and creating/destroying arrays in a loop at runtime.

Most drivers seem to detach their internal state from the struct
disk, and therefore they don't need this.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.