From owner-freebsd-current@FreeBSD.ORG Fri Feb 13 16:13:01 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E9BD1065677; Fri, 13 Feb 2009 16:13:01 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0E9908FC1D; Fri, 13 Feb 2009 16:13:01 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:d4b0:f1d4:1821:a4b] (unknown [IPv6:2001:7b8:3a7:0:d4b0:f1d4:1821:a4b]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 007575C44; Fri, 13 Feb 2009 17:12:59 +0100 (CET) Message-ID: <49959C0B.2020300@andric.com> Date: Fri, 13 Feb 2009 17:12:59 +0100 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b3pre) Gecko/20090213 Shredder/3.0b2pre MIME-Version: 1.0 To: John Baldwin References: <20090212123753.1602cb81@gluon> <4994CBE5.5090805@andric.com> <20090213043154.6ae1be31@tau.draftnet> <200902131001.29502.jhb@freebsd.org> In-Reply-To: <200902131001.29502.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Bruce Cran , freebsd-current@freebsd.org Subject: Re: Duplicate slice entries in /dev X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2009 16:13:01 -0000 On 2009-02-13 16:01, John Baldwin wrote: >>> Any chance you might have both GEOM_MBR and GEOM_PART_MBR in your >>> kernel configuration? >> I have both GEOM_PART_GPT and GEOM_MBR, but not GEOM_PART_MBR. > Since GEOM_PART_MBR is in DEFAULTS you effectively do have both of them in > there, however. Hmm, on my -CURRENT test box, I get this problem with duplicated /dev entries when I kldload GEOM_BSD (while GEOM_PART_BSD is already statically linked into the kernel). It seems GEOM_MBR isn't even needed: $ ls -l /dev/ad0* crw-r----- 1 root operator 0, 81 Feb 13 17:05 /dev/ad0 crw-r----- 1 root operator 0, 84 Feb 13 17:05 /dev/ad0a crw-r----- 1 root operator 0, 84 Feb 13 17:05 /dev/ad0a crw-r----- 1 root operator 0, 92 Feb 13 17:09 /dev/ad0aa crw-r----- 1 root operator 0, 93 Feb 13 17:09 /dev/ad0ab crw-r----- 1 root operator 0, 94 Feb 13 17:09 /dev/ad0ac crw-r----- 1 root operator 0, 85 Feb 13 17:05 /dev/ad0b crw-r----- 1 root operator 0, 85 Feb 13 17:05 /dev/ad0b crw-r----- 1 root operator 0, 97 Feb 13 17:09 /dev/ad0c Especially the ad0a[a-c] entries are funny, it seems to find a disklabel within a disklabel. :) Probably each of the geom modules registers the device(s) it found with devd, causing nodes to appear in devfs. Maybe these geom modules could be exclusionary, e.g. GEOM_PART_BSD should refuse to load, if GEOM_BSD is loaded, and vice versa? (And possibly the same for GEOM_PART_MBR and GEOM_MBR.)