From owner-freebsd-fs@FreeBSD.ORG  Sun Sep 12 18:32:43 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 AC93A106566B;
	Sun, 12 Sep 2010 18:32:43 +0000 (UTC)
	(envelope-from a.smith@ukgrid.net)
Received: from mx0.ukgrid.net (mx0.ukgrid.net [89.21.28.37])
	by mx1.freebsd.org (Postfix) with ESMTP id 13EE58FC0C;
	Sun, 12 Sep 2010 18:32:43 +0000 (UTC)
Received: from [89.21.28.38] (port=12139 helo=omicron.ukgrid.net)
	by mx0.ukgrid.net with esmtp (Exim 4.72; FreeBSD)
	envelope-from a.smith@ukgrid.net
	id 1OurM0-0008US-C7; Sun, 12 Sep 2010 19:32:40 +0100
Received: from voip.ukgrid.net (voip.ukgrid.net [89.107.16.9]) by
	webmail2.ukgrid.net (Horde Framework) with HTTP;
	Sun, 12 Sep 2010 19:32:40 +0100
Message-ID: <20100912193240.16694ph09065z484@webmail2.ukgrid.net>
Date: Sun, 12 Sep 2010 19:32:40 +0100
From: a.smith@ukgrid.net
To: Alexander Motin <mav@FreeBSD.org>
References: <20100909140000.5744370gkyqv4eo0@webmail2.ukgrid.net>
	<20100909182318.11133lqu4q4u1mw4@webmail2.ukgrid.net>
	<4C89D6A8.1080107@icyb.net.ua>
	<20100910143900.20382xl5bl6oo9as@webmail2.ukgrid.net>
	<20100910141127.GA13056@icarus.home.lan>
	<20100910155510.11831w104qjpyc4g@webmail2.ukgrid.net>
	<20100910152544.GA14636@icarus.home.lan>
	<20100910173912.205969tzhjiovf8c@webmail2.ukgrid.net>
	<4C8A6B26.8050305@icyb.net.ua>
	<20100910184921.16956kbaskhrsmg4@webmail2.ukgrid.net>
	<4C8A7B20.7090408@FreeBSD.org>
In-Reply-To: <4C8A7B20.7090408@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=ISO-8859-1;
 DelSp="Yes";
 format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.7) / FreeBSD-8.0
Cc: freebsd-fs@freebsd.org, Andriy Gapon <avg@icyb.net.ua>
Subject: Re: ZFS related kernel panic
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Sep 2010 18:32:43 -0000

Quoting Alexander Motin <mav@FreeBSD.org>:

>
> It looks like during timeout handling (it is quite complicated process
> when port multiplier is used) some request was completed twice. So
> original problem is probably in hardware (try to check/replace cables,
> multiplier, ...), that caused timeout, but the fact that drive was
> unable to handle it is probably a siis(4) driver bug.
>

Hi,

   about checking for faulty hardware, to recap... So far I have  
replaced the server, moved from i386 to amd64, and now I have also  
replaced the eSATA PCI card. With all of these changes I am still  
getting the panics.
On Monday I will swap out the drive enclosure and the cable which  
should cover off the things you mentioned. Once Ive tested that Ill  
let you know if Im still seeing the issue,

thanks Andy.

PS the disk enclosure is this:

http://uk.startech.com/product/S352U2RER-35in-eSATA-USB-Dual-SATA-Hot-Swap-External-RAID-Hard-Drive-Enclosure

Which according to the specs is using a Sil5744, I assume this is  
providing the port multiplier support. Just in case thats of any help,  
ie any know issues...