From owner-freebsd-fs@FreeBSD.ORG Wed Sep 19 07:36:24 2007 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6F0616A418 for ; Wed, 19 Sep 2007 07:36:24 +0000 (UTC) (envelope-from freebsd-fs@adam.gs) Received: from mail.adam.gs (mail.adam.gs [76.9.2.116]) by mx1.freebsd.org (Postfix) with ESMTP id 68C2D13C442 for ; Wed, 19 Sep 2007 07:36:24 +0000 (UTC) (envelope-from freebsd-fs@adam.gs) Received: from [127.0.0.1] (localhost.adam.gs [127.0.0.1]) by mail.adam.gs (Postfix) with ESMTP id 931A8F354AD for ; Wed, 19 Sep 2007 03:24:27 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=mail; d=adam.gs; b=UdIe9DWTAOtJoKU3g9jFzDLVIKJpU0NtDE+MARy76xhTKACBPSWO3Fh+tonm111XeyA5J74ARnsiLiRNI7BrdzU4crTz65kC+DHhX+KhjWf5C0n2Lcr02j+hYoO3dEcE8tCayXrg9ikEImU9Rq6PmcHxNE1oAkUBpk0HPonGJv8=; Received: from [10.0.1.125] (unknown [64.111.192.110]) (Authenticated sender: adam@adam.gs) by mail.adam.gs (Postfix) with ESMTP id 229A6F34D64; Wed, 19 Sep 2007 03:24:27 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org From: Adam Jacob Muller Date: Wed, 19 Sep 2007 03:24:25 -0400 X-Mailer: Apple Mail (2.752.3) Cc: Subject: ZFS pool not working on boot X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Sep 2007 07:36:24 -0000 Hello, I have a server with two ZFS pools, one is an internal raid0 using 2 drives connected via ahc. The other is an external storage array with 11 drives also using ahc, using raidz. (This is a dell 1650 and pv220s). On reboot, the pools do not come online on their own. Both pools consistently show as failed. the exact symptoms vary, however I have seen that many drives are marked as variously "corrupt" or "unavailable" most zpool operations fail with "pool is unavailable" errors. Here is the interesting part. Consistently, 100% of the time, a zpool export followed by a zpool import restores the arrays to an ONLINE status. Once the array is online, it's quite stable (I'm loving ZFS btw, thank you to everyone for the hard work on this, ZFS is fantastic) and works great. Anyone have any ideas why this might occur and what/if the solution is? Any additional information can be provided on-request, I am running current from approximately 1 week ago. -Adam