From owner-freebsd-current@FreeBSD.ORG  Fri Dec 19 04:53:18 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 795D816A4CE
	for <current@freebsd.org>; Fri, 19 Dec 2003 04:53:18 -0800 (PST)
Received: from mail.evip.pl (mail.evip.com.pl [212.244.157.179])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1703943D1F
	for <current@freebsd.org>; Fri, 19 Dec 2003 04:53:17 -0800 (PST)
	(envelope-from w@evip.pl)
Received: from drwebc by mail.evip.pl with drweb-scanned (Exim 4.22)
	id 1AXK84-0001V8-AZ; Fri, 19 Dec 2003 13:53:16 +0100
Received: from w by mail.evip.pl with local (Exim 4.22)
	id 1AXK84-0001V2-7l; Fri, 19 Dec 2003 13:53:16 +0100
Date: Fri, 19 Dec 2003 13:53:16 +0100
From: Wiktor Niesiobedzki <bsd@w.evip.pl>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Message-ID: <20031219125316.GB3682@mail.evip.pl>
References: <20031219122146.GA3682@mail.evip.pl>
	<6723.1071837091@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6723.1071837091@critter.freebsd.dk>
User-Agent: Mutt/1.4i
Sender: Wiktor Niesiobedzki <w@evip.pl>
cc: current@freebsd.org
Subject: Re: GEOM oddity with verbose boot
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2003 12:53:18 -0000

On Fri, Dec 19, 2003 at 01:31:31PM +0100, Poul-Henning Kamp wrote:
> In message <20031219122146.GA3682@mail.evip.pl>, Wiktor Niesiobedzki writes:
> 
> >Just an observation:
> >When I boot in verbose mode I get:
> >GEOM: Configure ad6s1, start 32256 length 80026329600 end 80026361855
> >GEOM: Configure ad6s1a, start 0 length 1073741824 end 1073741823
> >GEOM: Configure ad6s1b, start 1073741824 length 1073741824 end 2147483647
> >GEOM: Configure ad6s1c, start 0 length 80026329600 end 80026329599
> >GEOM: Configure ad6s1d, start 2147483648 length 21474836480 end 23622320127
> >GEOM: Configure ad6s1e, start 23622320128 length 56404009472 end 80026329599
> >GEOM: Configure ad6s1da, start 8192 length 80026321408 end 80026329599
> >GEOM: Configure ad6s1db, start 1073741824 length 1073741824 end 2147483647
> >GEOM: Configure ad6s1dc, start 0 length 80026329600 end 80026329599
> >GEOM: Configure ad6s1dd, start 0 length 1073741824 end 1073741823
> >GEOM: Configure ad6s1de, start 2147483648 length 21474836480 end 23622320127
> >
> >Entries for ad6s1d* are the suspicous one.
> 
> You seem to have (most of) a valid BSD label in your ad6s1d parition.
> 
> Try 
> 	bsdlabel ad6s1d
> 
> I'm pretty sure it finds a label for you. 
Ofcourse, it finds, but what makes me worry, is how there could be a valid bsd
label, if there is a valid UFS2 superblock?
If I understand correctly, in first 8192 bytes of partition are at the same
time:
- UFS2 superblock
- BSD label

Is that just a coincidence? Should it be possible?


Cheers,

Wiktor Niesiobedzki