From owner-freebsd-arch@FreeBSD.ORG Mon Sep 13 19:35:54 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8634116A4CE for ; Mon, 13 Sep 2004 19:35:54 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id B842343D1F for ; Mon, 13 Sep 2004 19:35:53 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i8DJZqui083279; Mon, 13 Sep 2004 21:35:52 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Sam From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 13 Sep 2004 15:12:17 CDT." Date: Mon, 13 Sep 2004 21:35:52 +0200 Message-ID: <83278.1095104152@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-arch@freebsd.org Subject: Re: 4.x device failure? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2004 19:35:54 -0000 In message , Sam writes: >Ah. Well that answers it. I'll fail unloading of the >module if devices are open. > >This leads to a curiosity as to how the RAID >failover modules work at all. I guess if you abstract >the real disk(s) under a logical disk you can change >the bottom layer without affecting the top. I'll have >to look at that code a little closer. You should really start to study GEOM in 5.x which gives a nice clean framework for all this sort of stuff. You can start here for instance: http://phk.freebsd.dk/pubs/bsdcan-04.slides.geomtut.pdf -- 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.