From owner-freebsd-fs@FreeBSD.ORG  Fri Oct 10 01:27:34 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D39D5446;
 Fri, 10 Oct 2014 01:27:34 +0000 (UTC)
Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "mouf.net", Issuer "mouf.net" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 94DB0A4B;
 Fri, 10 Oct 2014 01:27:34 +0000 (UTC)
Received: from mouf.net (swills@mouf [199.48.129.64])
 by mouf.net (8.14.5/8.14.5) with ESMTP id s9A1RRRF078213
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
 Fri, 10 Oct 2014 01:27:32 GMT (envelope-from swills@mouf.net)
Received: (from swills@localhost)
 by mouf.net (8.14.5/8.14.5/Submit) id s9A1RRNH078212;
 Fri, 10 Oct 2014 01:27:27 GMT (envelope-from swills)
Date: Fri, 10 Oct 2014 01:27:27 +0000
From: Steve Wills <swills@freebsd.org>
To: Andriy Gapon <avg@freebsd.org>
Subject: Re: zfs hang
Message-ID: <20141010012724.GD79158@mouf.net>
References: <20141008004045.GA24762__48659.9047123038$1412728878$gmane$org@mouf.net>
 <5434D1CE.8010801@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5434D1CE.8010801@FreeBSD.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (mouf.net [199.48.129.64]); Fri, 10 Oct 2014 01:27:33 +0000 (UTC)
X-Spam-Status: No, score=0.0 required=4.5 tests=HEADER_FROM_DIFFERENT_DOMAINS
 autolearn=unavailable autolearn_force=no version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mouf.net
X-Virus-Scanned: clamav-milter 0.98.3 at mouf.net
X-Virus-Status: Clean
Cc: current@freebsd.org, fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
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: Fri, 10 Oct 2014 01:27:34 -0000

On Wed, Oct 08, 2014 at 08:55:26AM +0300, Andriy Gapon wrote:
> On 08/10/2014 03:40, Steve Wills wrote:
> > Hi,
> > 
> > Not sure which thread this belongs to, but I have a zfs hang on one of my boxes
> > running r272152. Running procstat -kka looks like:
> > 
> > http://pastebin.com/szZZP8Tf
> > 
> > My zpool commands seem to be hung in spa_errlog_lock while others are hung in
> > zfs_lookup. Suggestions?
> 
> There are several threads in zio_wait.  If this is their permanent state then
> there is some problem with I/O somewhere below ZFS.

Thanks for the feedback. It seems one of my disks is dying, I rebooted and it
came up OK, but today I got:

  panic: I/O to pool 'rpool' appears to be hung on vdev guid ..... at '/dev/ada0p3'

I have screenshots and backtrace if anyone is interested. Dying drives
shouldn't cause panic, right?

Steve