From owner-freebsd-stable@FreeBSD.ORG  Sun Jan 27 13:24:21 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0294E16A478
	for <freebsd-stable@freebsd.org>; Sun, 27 Jan 2008 13:24:21 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10])
	by mx1.freebsd.org (Postfix) with ESMTP id 6981913C458
	for <freebsd-stable@freebsd.org>; Sun, 27 Jan 2008 13:24:20 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by cs1.cs.huji.ac.il with esmtp
	id 1JJ7Ug-00004s-CH; Sun, 27 Jan 2008 15:24:18 +0200
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: Ivan Voras <ivoras@freebsd.org>
In-reply-to: <fng55e$pk7$2@ger.gmane.org> 
References: <479A0731.6020405@skyrush.com>
	<20080125162940.GA38494@eos.sc1.parodius.com>
	<479A3764.6050800@skyrush.com>
	<3803988D-8D18-4E89-92EA-19BF62FD2395@mac.com>
	<479A4CB0.5080206@skyrush.com>
	<20080126003845.GA52183@eos.sc1.parodius.com>
	<20080126010054.GA52891@eos.sc1.parodius.com>
	<20080126010653.GA53255@eos.sc1.parodius.com>
	<479A8A24.5050409@skyrush.com>
	<20080126012557.GB53400@eos.sc1.parodius.com>
	<479B1172.4050706@restart.be> <fng55e$pk7$2@ger.gmane.org>
Comments: In-reply-to Ivan Voras <ivoras@freebsd.org>
	message dated "Sat, 26 Jan 2008 21:28:29 +0100."
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 27 Jan 2008 15:24:18 +0200
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1JJ7Ug-00004s-CH@cs1.cs.huji.ac.il>
Cc: freebsd-stable@freebsd.org
Subject: Re: "ad0: TIMEOUT - WRITE_DMA" type errors with 7.0-RC1 
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jan 2008 13:24:21 -0000


> Henri Hennebert wrote:
> > Jeremy Chadwick wrote:
> >> On Fri, Jan 25, 2008 at 06:17:24PM -0700, Joe Peterson wrote:
> >>> Glad you got it back!  Yes, when I was first playing with ZFS, I noti=
> ced
> >>> that booting between single and multi user mode could make the pools
> >>> "invisible".  Import seemed to bring them back...
> >>
> >> I did go into single-user mode and attempt to do ZFS-related commands,=
> 
> >> which might explain the "no datasets available" once I was back in
> >> multiuser!  I would classify that as a bug, and one which is going to
> >> cause all sorts of hair-pulling for administrators in the future.  I
> >> wonder what it's caused by.
> >=20
> > In single user / is read only and so /boot/zfs/zpool.cache can't be=20
> > created/updated
> 
> But it's still readable. The issue is that hostid isn't set (by=20
> /etc/rc.d/hostid).

if the root is read only, as the case of diskless/dataless boot, it's
the fact that /boot/zfs/zpool.cache cannot be used which causes
the problem, so adding zpool import -a solves the issue.

danny