From owner-freebsd-current@FreeBSD.ORG Thu Jul 4 09:03:42 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2AD9DFF5 for ; Thu, 4 Jul 2013 09:03:42 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from zcs03.jnb1.cloudseed.co.za (zcs03.jnb1.cloudseed.co.za [41.154.0.139]) by mx1.freebsd.org (Postfix) with ESMTP id BFE7818B5 for ; Thu, 4 Jul 2013 09:03:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zcs03.jnb1.cloudseed.co.za (Postfix) with ESMTP id EC9072B4323E; Thu, 4 Jul 2013 11:03:33 +0200 (SAST) X-Virus-Scanned: amavisd-new at zcs03.jnb1.cloudseed.co.za Received: from zcs03.jnb1.cloudseed.co.za ([127.0.0.1]) by localhost (zcs03.jnb1.cloudseed.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IZ09Mo-k2n9E; Thu, 4 Jul 2013 11:03:33 +0200 (SAST) Received: from clue.co.za (unknown [41.154.88.19]) by zcs03.jnb1.cloudseed.co.za (Postfix) with ESMTPSA id 2B19F2B4320D; Thu, 4 Jul 2013 11:03:33 +0200 (SAST) Received: from localhost ([127.0.0.1] helo=zen.clue.co.za) by clue.co.za with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UufRq-0001sg-HG; Thu, 04 Jul 2013 11:03:30 +0200 To: Konstantin Belousov From: Ian FREISLICH Subject: Re: Filesystem wedges caused by r251446 In-Reply-To: <20130704082113.GJ91021@kib.kiev.ua> References: <20130704082113.GJ91021@kib.kiev.ua> X-Attribution: BOFH Date: Thu, 04 Jul 2013 11:03:29 +0200 Message-Id: Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jul 2013 09:03:42 -0000 Konstantin Belousov wrote: > > Care to provide any useful information ? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html Well, the system doesn't deadlock it's perfectly useable so long as you don't touch the file that's wedged. A lot of the time the userland process is unkillable, but often it is killable. How do I get from from the PID to where the FS is stuck in the kernel? Ian -- Ian Freislich