From owner-freebsd-current@FreeBSD.ORG Sat Feb 21 14:34:03 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECAAD1065672 for ; Sat, 21 Feb 2009 14:34:03 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from hercules.mthelicon.com (hercules.mthelicon.com [IPv6:2001:49f0:2023::2]) by mx1.freebsd.org (Postfix) with ESMTP id B7E8B8FC12 for ; Sat, 21 Feb 2009 14:34:03 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from feathers.peganest.com (78-33-110-3.static-adsl.entanet.co.uk [78.33.110.3] (may be forged)) (authenticated bits=0) by hercules.mthelicon.com (8.14.3/8.14.3) with ESMTP id n1LEY1E8043393 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Sat, 21 Feb 2009 14:34:03 GMT (envelope-from ken@mthelicon.com) From: Pegasus Mc Cleaft Organization: Feathers To: current@freebsd.org Date: Sat, 21 Feb 2009 14:33:54 +0000 User-Agent: KMail/1.11.0 (FreeBSD/8.0-CURRENT; KDE/4.2.0; amd64; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902211433.54247.ken@mthelicon.com> Cc: Subject: ZFS corruption with -current(21/02/2009) on AMD64 w/ ZFS boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2009 14:34:04 -0000 Hi Current, I am having a horrible time with the latest current (21/02/2009) with my AMD64 machine and ZFS boot. The kernel appears to load OK, but when it tries to mount the root filing system from the ZFS pool, it mounts but starts to corrupt the data on the drives. It is unable to mount the zraid pools/filing systems and the machine just goes to a login prompt. In the configuration I have, I use a zraid pool for all /usr /var and /local, the rest is off a 3 way mirror for / The only way out of this is to physically disconnect the corrupted drive and boot off one of the mirrors with the previous kernel (The last one what works for me is -Current 14/02/2009). Once the system is booted, normally I have to remove the faulted drive, reattach it to the mirror and let the system resilver. dmesg outputs look like: Feb 21 14:16:56 feathers root: ZFS: vdev failure, zpool=PegaBoot2 type=vdev.corrupt_data Feb 21 14:16:58 feathers root: ZFS: vdev failure, zpool=PegaBoot2 type=vdev.corrupt_data Feb 21 14:17:08 feathers su: ken to root on /dev/pts/1 Feb 21 14:17:29 feathers root: ZFS: vdev failure, zpool=PegaBoot2 type=vdev.corrupt_data Feb 21 14:18:00 feathers last message repeated 2 times Feb 21 14:18:00 feathers root: ZFS: vdev failure, zpool=PegaBoot2 type=vdev.corrupt_data If there is any more information that I can give that will be helpfull, please let me know.. Peg