From owner-freebsd-stable@FreeBSD.ORG Tue May 17 12:38:39 2011 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C73251065675 for ; Tue, 17 May 2011 12:38:39 +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 1AA508FC12 for ; Tue, 17 May 2011 12:38:38 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA25595; Tue, 17 May 2011 15:38:33 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4DD26C49.4010108@FreeBSD.org> Date: Tue, 17 May 2011 15:38:33 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Jeremy Chadwick References: <20110517073029.GA44359@icarus.home.lan> <4DD25264.8040305@FreeBSD.org> <20110517112952.GA48610@icarus.home.lan> <4DD2624A.9080708@FreeBSD.org> <20110517122323.GA49650@icarus.home.lan> In-Reply-To: <20110517122323.GA49650@icarus.home.lan> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Charles Sprickman , stable@FreeBSD.org Subject: Re: 8.1R possible zfs snapshot livelock? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 12:38:39 -0000 on 17/05/2011 15:23 Jeremy Chadwick said the following: > So for Charles' situation, the next time it happens what would be useful > for him to provide? The best I could come up with was to induce doadump > then reboot to get the system up/working again, and then use kgdb > after-the-fact. This is one of the best things to do, if possible. In this case all the potentially useful info would be preserved. Less drastic approach to hanged I/O debugging is to find out where processes/threads are actually stuck. E.g. using procstat -kk. -- Andriy Gapon