From owner-freebsd-current@FreeBSD.ORG Fri May 9 14:10:48 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56EE837B401 for ; Fri, 9 May 2003 14:10:48 -0700 (PDT) Received: from MX1.estpak.ee (ld1.estpak.ee [194.126.101.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1175543F3F for ; Fri, 9 May 2003 14:10:47 -0700 (PDT) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-42-96-dsl.mus.estpak.ee [80.235.42.96]) by MX1.estpak.ee (Postfix) with ESMTP id 6FCF7887E9; Sat, 10 May 2003 00:09:11 +0300 (EEST) Received: (from vallo@localhost) by kevad.internal (8.12.9/8.12.9/Submit) id h49EAjuB006987; Fri, 9 May 2003 17:10:45 +0300 (EEST) (envelope-from vallo) Date: Fri, 9 May 2003 17:10:45 +0300 From: Vallo Kallaste To: Poul-Henning Kamp Message-ID: <20030509141045.GA6835@kevad.internal> References: <20030509052145.GA595@kevad.internal> <13473.1052511292@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13473.1052511292@critter.freebsd.dk> User-Agent: Mutt/1.5.4i-ja.1 cc: freebsd-current@freebsd.org Subject: Re: GEOM loose end? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kalts@estpak.ee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2003 21:10:48 -0000 On Fri, May 09, 2003 at 10:14:52PM +0200, Poul-Henning Kamp wrote: > >third slice is there. The only thing missing is now /dev entry for > >this slice, there's no /dev/adXs3. This /dev entry will be created > >when I reboot the system, but that's not acceptable. Any workaround? > > Unfortunately, I don't have time to work much on this issue, just > getting the kernel side and the basic tools (bsdlabel(8), sunlabel(8) > etc in shape takes most of the time I have. > > Try using "bsdlabel -e" next time, it is not as hard as you might > fear. Ok, I'm actually not that inexperienced wrt to disklabel, as you might guess :) Anyway, there seems to be some misunderstanding, as I was talking about disk slices, not disk labels. I can't put label on the slice when the device node is missing in the first case. Bsdlabel -e is useless in this case, no? Will bsdlabel "notify" geom in some way about missing node so it will be created on the fly? Can't try it myself in the coming two days or so. -- Vallo Kallaste