ZFS corruption with -current(21/02/2009) on AMD64 w/ ZFS boot

From: Pegasus Mc Cleaft <ken_at_mthelicon.com>
Date: Sat, 21 Feb 2009 14:33:54 +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
Received on Sat Feb 21 2009 - 13:34:03 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:42 UTC