From owner-freebsd-fs@FreeBSD.ORG Sun Nov 11 08:13:20 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1BC23DB2 for ; Sun, 11 Nov 2012 08:13:20 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5DAD98FC0C for ; Sun, 11 Nov 2012 08:13:18 +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 KAA09476; Sun, 11 Nov 2012 10:13:01 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TXSf7-0008fq-F6; Sun, 11 Nov 2012 10:13:01 +0200 Message-ID: <509F5E0A.1020501@FreeBSD.org> Date: Sun, 11 Nov 2012 10:12:58 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: Peter Jeremy Subject: Re: zfs diff deadlock References: <20121110223249.GB506@server.rulingia.com> <20121111072739.GA4814@server.rulingia.com> In-Reply-To: <20121111072739.GA4814@server.rulingia.com> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 08:13:20 -0000 on 11/11/2012 09:27 Peter Jeremy said the following: > On 2012-Nov-11 09:32:49 +1100, Peter Jeremy > wrote: >> I recently decided to do a "zfs diff" between two snapshots to try and >> identify why there was so much "USED" space in the snapshot. The diff ran >> for a while (though with very little IO) but has now wedged unkillably. >> There's nothing on the console or in any logs, the pool reports no >> problems and there are no other visible FS issues. Any ideas on tracking >> this down? > ... >> The systems is running a 4-month old 8-stable (r237444) > > I've tried a second system running the same world with the same result, so > this looks like a real bug in ZFS rather than a system glitch. > Are you able to catch the state of all threads in the system? E.g. via procstat -k -a. Or a crash dump. -- Andriy Gapon