From owner-freebsd-stable@FreeBSD.ORG  Sat Jan 26 01:17:08 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 0F39516A41A;
	Sat, 26 Jan 2008 01:17:08 +0000 (UTC) (envelope-from joe@skyrush.com)
Received: from shadow.wildlava.net (shadow.wildlava.net [67.40.138.81])
	by mx1.freebsd.org (Postfix) with ESMTP id CC53013C468;
	Sat, 26 Jan 2008 01:17:07 +0000 (UTC) (envelope-from joe@skyrush.com)
Received: from [10.0.3.98] (mail.boulder.swri.edu [65.241.78.2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by shadow.wildlava.net (Postfix) with ESMTP id 8F5FE8F448;
	Fri, 25 Jan 2008 18:17:06 -0700 (MST)
Message-ID: <479A8A24.5050409@skyrush.com>
Date: Fri, 25 Jan 2008 18:17:24 -0700
From: Joe Peterson <joe@skyrush.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071119)
MIME-Version: 1.0
To: Jeremy Chadwick <koitsu@FreeBSD.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>
In-Reply-To: <20080126010653.GA53255@eos.sc1.parodius.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Sat, 26 Jan 2008 01:17:08 -0000

Glad you got it back!  Yes, when I was first playing with ZFS, I noticed
that booting between single and multi user mode could make the pools
"invisible".  Import seemed to bring them back...

So, is the disk toast, or can you still read anything from it (part
table, etc.)?

	-Joe


Jeremy Chadwick wrote:
> On Fri, Jan 25, 2008 at 05:00:54PM -0800, Jeremy Chadwick wrote:
>> icarus# zfs list
>> no datasets available
>>
>> This doesn't bode well, and doesn't make me happy.  At all.
> 
> Pshew!  I was able to get ZFS to start seeing the pool again by doing
> the following:  (Supposedly "zpool import" by itself will show you a
> list of pools which it manages to see...")
> 
> icarus# zpool import -f storage
> icarus# df -k /storage
> Filesystem  1024-blocks      Used     Avail Capacity  Mounted on
> storage       957873024 106124032 851748992    11%    /storage
> icarus# zfs list
> NAME      USED  AVAIL  REFER  MOUNTPOINT
> storage   101G   812G   101G  /storage
> icarus# zpool status
>   pool: storage
>  state: ONLINE
>  scrub: none requested
> config:
> 
>         NAME        STATE     READ WRITE CKSUM
>         storage     ONLINE       0     0     0
>           ad8       ONLINE       0     0     0
>           ad10      ONLINE       0     0     0
> 
> errors: No known data errors
> 
> Back to the drawing board.
>