From owner-freebsd-current@FreeBSD.ORG Fri Sep 25 08:20:43 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA5DE106568D; Fri, 25 Sep 2009 08:20:43 +0000 (UTC) (envelope-from james-freebsd-current@jrv.org) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.freebsd.org (Postfix) with ESMTP id 441728FC0C; Fri, 25 Sep 2009 08:20:38 +0000 (UTC) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.3/8.14.3) with ESMTP id n8P8KVT0070141; Fri, 25 Sep 2009 03:20:31 -0500 (CDT) (envelope-from james-freebsd-current@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=james-freebsd-current@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=CYAo6opoYmUSc5b47rY6TuTKXiscje3lQASdC4aRjqCNhW/JXlXlVzbIosXsMjJ8F Pw0Duu0GcwFhAwvBG7+8Nu68WjHofizqYT9VqwZcGlHzwUDAu8xvwfokgPO3lw4SXMT 4PV51dAoK1mXpY4DfgJ7yJ17Muf/VT65nbGiwRQ= Message-ID: <4ABC7D4F.3000202@jrv.org> Date: Fri, 25 Sep 2009 03:20:31 -0500 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Pegasus Mc Cleaft References: <200909212027.49752.ken@mthelicon.com> In-Reply-To: <200909212027.49752.ken@mthelicon.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Alexander Motin , FreeBSD Current Subject: Re: SIIS timeout with current r197392: 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: Fri, 25 Sep 2009 08:20:43 -0000 Pegasus Mc Cleaft wrote: > Hello Current, > > Since my latest build of amd64-current kernel and world (r197392) I am > getting strange timeout errors in my dmesg and eventual system instability. I believe mav has stated that error handling in SIIS isn't finished or is problematic in some way. I see similar problems: most of the time an error results in a hung device, requiring reboot. This usually happens within a TB or two or intense I/O: I have not yet seen a 6 TB ZFS pool complete a "scrub" due to this.