From owner-cvs-src@FreeBSD.ORG Fri Nov 18 15:10:33 2005 Return-Path: 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 7701916A41F; Fri, 18 Nov 2005 15:10:33 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC86143D46; Fri, 18 Nov 2005 15:10:32 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAIFAU5i099073; Fri, 18 Nov 2005 08:10:31 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <437DEEE5.9040201@samsco.org> Date: Fri, 18 Nov 2005 08:10:29 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <7052.1132309178@critter.freebsd.dk> In-Reply-To: <7052.1132309178@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: John Polstra , cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, Lukas Ertl 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 15:10:33 -0000 Poul-Henning Kamp wrote: > 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. > So what makes CAM special in this regard? Scott