Bad hardware + zfs = panic

[Ståle Kristoffersen]

On 2010-05-12 at 13:08, Pawel Jakub Dawidek wrote:
> On Wed, May 12, 2010 at 12:21:56PM +0200, Pawel Jakub Dawidek wrote:

<removed panic>

> > Well, I don't think it should be possible for vdev to be NULL.
> > But if you still have this panic, can you try this patch:
> > 
> > 	http://people.freebsd.org/~pjd/patches/vdev_mirror.c.patch

Yeah, it shouldn't be possible, but I had something in my system that
corrupted data in memory, and that can lead to all sorts of problems. I'm not
blaming ZFS for not handling 'impossible' situations, but this seemed like
something that could be avoided. I'm actually impressed with how well ZFS
handled it, my UFS root-fs went ballistic a few times.

> It looks like:
> 
> 	http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6435666
> 
> The work-around is to remove /boot/zfs/zpool.cache and import the pool
> again.

Fortunately I found out which file was problematic, and after removing it
and recreating it, I've had no more panics. I'm not sure if the tip on that
page would have solved the problem, because zpool.cache is removed on my
system when exporting the pool.

Thanks for the help tho, everything looks to be working now :)
-- 
Ståle Kristoffersen
staalebk at ifi.uio.no