From owner-freebsd-geom@FreeBSD.ORG Wed Feb 9 23:17:24 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B36016A4CE for ; Wed, 9 Feb 2005 23:17:24 +0000 (GMT) Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id B73AC43D1F for ; Wed, 9 Feb 2005 23:17:23 +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 j19NHL4U003534; Thu, 10 Feb 2005 00:17:21 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 10 Feb 2005 00:14:40 +0100." <86y8dxiavz.fsf@dwp.des.no> Date: Thu, 10 Feb 2005 00:17:21 +0100 Message-ID: <3533.1107991041@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: geom@freebsd.org Subject: Re: getting a little carried away? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2005 23:17:24 -0000 In message <86y8dxiavz.fsf@dwp.des.no>, =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= writes: >this box has a RAID-1 array with a single slice containing six >partitions: > >des@dwp ~% ls /dev/ar0* >/dev/ar0 /dev/ar0s1a /dev/ar0s1c /dev/ar0s1e /dev/ar0s1g >/dev/ar0s1 /dev/ar0s1b /dev/ar0s1d /dev/ar0s1f > >the components of ar0 are ad4 and ad6. I realize that a component in >a RAID-1 array "tastes the same" to GEOM as a standalone disk, but I >think this is a bit much, especially the adMcsN stuff: > >des@dwp ~% ls /dev/ad[46]* >/dev/ad4 /dev/ad4cs1f /dev/ad4s1e /dev/ad6cs1c /dev/ad6s1b >/dev/ad4a /dev/ad4cs1g /dev/ad4s1f /dev/ad6cs1d /dev/ad6s1c >/dev/ad4b /dev/ad4d /dev/ad4s1g /dev/ad6cs1e /dev/ad6s1d >/dev/ad4c /dev/ad4e /dev/ad6 /dev/ad6cs1f /dev/ad6s1e >/dev/ad4cs1 /dev/ad4f /dev/ad6a /dev/ad6cs1g /dev/ad6s1f >/dev/ad4cs1a /dev/ad4s1 /dev/ad6b /dev/ad6d /dev/ad6s1g >/dev/ad4cs1b /dev/ad4s1a /dev/ad6c /dev/ad6e >/dev/ad4cs1c /dev/ad4s1b /dev/ad6cs1 /dev/ad6f >/dev/ad4cs1d /dev/ad4s1c /dev/ad6cs1a /dev/ad6s1 >/dev/ad4cs1e /dev/ad4s1d /dev/ad6cs1b /dev/ad6s1a > >is this normal? more to the point, is it desirable? yes and yes. -- 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.