From owner-freebsd-current@FreeBSD.ORG  Mon May  5 15:52:20 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 D025537B448
	for <current@freebsd.org>; Mon,  5 May 2003 15:52:20 -0700 (PDT)
Received: from postal3.es.net (postal3.es.net [198.128.3.207])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 81FCA43F3F
	for <current@freebsd.org>; Mon,  5 May 2003 15:51:47 -0700 (PDT)
	(envelope-from oberman@es.net)
Received: from ptavv.es.net ([198.128.4.29])
        by postal3.es.net (Postal Node 3) with ESMTP id MUA74016
        for <current@freebsd.org>; Mon, 05 May 2003 15:51:45 -0700
Received: from ptavv (localhost [127.0.0.1])
	by ptavv.es.net (Tachyon Server) with ESMTP id 6C3615D04
	for <current@freebsd.org>; Mon,  5 May 2003 15:51:45 -0700 (PDT)
To: current@freebsd.org
Date: Mon, 05 May 2003 15:51:45 -0700
From: "Kevin Oberman" <oberman@es.net>
Message-Id: <20030505225145.6C3615D04@ptavv.es.net>
Subject: State of disk support in CURRENT
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: Mon, 05 May 2003 22:52:21 -0000

I've had a really fun few days with current. Due to a family emergency I
was off-line for several days and my subscription to current was disabled
due to a mail problem at my site on April 30. So I missed quite a few
messages. :-( 
(Yes, I have been scanning through the lost stuff in the archive.) 

After almost two days of building I have a stable CURRENT again.

I do see one troubling message at boot:
WARNING: Expected rawoffset 31479840, found 0

I get the same message when using dd(1) to make a copy if the disk to an
identical drive. The expected rawoffset is the location of the slice
used for FreeBSD. Since my previous kernel was unable to mount the root
partition, I find this a at least a little concern, but have not looked
for the source that generates this due to being swamped by my day job
after 2weeks away.

Do I have a problem I need to worry about?

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634