From owner-freebsd-fs@FreeBSD.ORG  Sat Apr 13 08:31:08 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id DFEE582F
 for <freebsd-fs@freebsd.org>; Sat, 13 Apr 2013 08:31:08 +0000 (UTC)
 (envelope-from quartz@sneakertech.com)
Received: from relay03.pair.com (relay03.pair.com [209.68.5.17])
 by mx1.freebsd.org (Postfix) with SMTP id 84323853
 for <freebsd-fs@freebsd.org>; Sat, 13 Apr 2013 08:31:08 +0000 (UTC)
Received: (qmail 84369 invoked by uid 0); 13 Apr 2013 08:31:06 -0000
Received: from 173.48.104.62 (HELO ?10.2.2.1?) (173.48.104.62)
 by relay03.pair.com with SMTP; 13 Apr 2013 08:31:06 -0000
X-pair-Authenticated: 173.48.104.62
Message-ID: <516917CA.5040607@sneakertech.com>
Date: Sat, 13 Apr 2013 04:31:06 -0400
From: Quartz <quartz@sneakertech.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Jeremy Chadwick <jdc@koitsu.org>
Subject: Re: A failed drive causes system to hang
References: <mailman.11.1365681601.78138.freebsd-fs@freebsd.org>
 <51672164.1090908@o2.pl> <20130411212408.GA60159@icarus.home.lan>
 <5168821F.5020502@o2.pl> <20130412220350.GA82467@icarus.home.lan>
In-Reply-To: <20130412220350.GA82467@icarus.home.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Sat, 13 Apr 2013 08:31:08 -0000

>If the ZFS layer
> is waiting on CAM, and CAM is waiting on your hardware, then those I/O
> requests are going to block indefinitely.

> 2. I agree that the problem is not likely in ZFS, but rather either with
> CAM, the AHCI implementation used, or hardware (either disk or storage
> controller).

Question:

How (or does) this relate to the hang that I'm seeing with my system? 
You mentioned cam issues when talking to me earlier, but less decisively 
than your comment here. What's the difference?


> We're also
> going to need to see "zpool status" output, as well as "zpool get all"
> and "zfs get all".  "pciconf -lvbc" would also be useful.

You never asked for these when talking to me, but I can provide any of 
it if you want to look at it.

______________________________________
it has a certain smooth-brained appeal