From owner-freebsd-fs@FreeBSD.ORG Wed Oct 8 05:56:33 2014 Return-Path: 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 F134B903; Wed, 8 Oct 2014 05:56:32 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E4F02A99; Wed, 8 Oct 2014 05:56:31 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id IAA22718; Wed, 08 Oct 2014 08:56:24 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1XbkEZ-0000Io-Qj; Wed, 08 Oct 2014 08:56:23 +0300 Message-ID: <5434D1CE.8010801@FreeBSD.org> Date: Wed, 08 Oct 2014 08:55:26 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Steve Wills Subject: Re: zfs hang References: <20141008004045.GA24762__48659.9047123038$1412728878$gmane$org@mouf.net> In-Reply-To: <20141008004045.GA24762__48659.9047123038$1412728878$gmane$org@mouf.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Oct 2014 05:56:33 -0000 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. -- Andriy Gapon