From owner-freebsd-stable@FreeBSD.ORG Sun Jul 28 06:25:57 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6433B2BB for ; Sun, 28 Jul 2013 06:25:57 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C2BF92287 for ; Sun, 28 Jul 2013 06:25:56 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r6S6Pj6k006535; Sun, 28 Jul 2013 09:25:45 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r6S6Pj6k006535 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r6S6PjIP006534; Sun, 28 Jul 2013 09:25:45 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 28 Jul 2013 09:25:45 +0300 From: Konstantin Belousov To: Michael Tratz Subject: Re: NFS deadlock on 9.2-Beta1 Message-ID: <20130728062545.GE4972@kib.kiev.ua> References: <780BC2DB-3BBA-4396-852B-0EBDF30BF985@esosoft.com> <806421474.2797338.1374956449542.JavaMail.root@uoguelph.ca> <20130727205815.GC4972@kib.kiev.ua> <602747E8-0EBE-4BB1-8019-C02C25B75FA1@esosoft.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HeFlAV5LIbMFYYuh" Content-Disposition: inline In-Reply-To: <602747E8-0EBE-4BB1-8019-C02C25B75FA1@esosoft.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: Steven Hartland , Rick Macklem , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jul 2013 06:25:57 -0000 --HeFlAV5LIbMFYYuh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 27, 2013 at 03:13:05PM -0700, Michael Tratz wrote: > Let's assume the pid which started the deadlock is 14001 (it will be a di= fferent pid when we get the results, because the machine has been restarted) >=20 > I type: >=20 > show proc 14001 >=20 > I get the thread numbers from that output and type: >=20 > show thread xxxxx >=20 > for each one. >=20 > And a trace for each thread with the command? >=20 > tr xxxx >=20 > Anything else I should try to get or do? Or is that not the data at all y= ou are looking for? >=20 Yes, everything else which is listed in the 'debugging deadlocks' page must be provided, otherwise the deadlock cannot be tracked. The investigator should be able to see the whole deadlock chain (loop) to make any useful advance. --HeFlAV5LIbMFYYuh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJR9LloAAoJEJDCuSvBvK1BZKEQAKJPVA6C86tsBJ9zeLnHFsaf 2CV/2o3i3cduDJCCslQ0Af8oWjebfEAmESUdd6aW8QVN2b6UMJxXj1DZTF/NOStR c0oL53FMSu9fUEQs0SJ/vcqLNt7iVgaY7ytgzwtDp1jESQlMcP0H+XLPqXf9p0i8 YOwcso1LPabMulxayWr44xwlVjDluIuLXAc1FGe9Y6tRE8i4RZtsB24zAIk/Svv1 d0wrGWkLZL2Eh6G1niOPu71lRw9TqJRlu/J8r01onVoXL7apEQTjLhTro/COXmgg 5QMG6o/unsO+aCLrPwmi3TYNqBZe5asub8HIPfXYSgbi7VAOlY/ZsHAHvVRi5fTC DMuE7cCgqGXI+Yz3FauoYlsq5pDcAhcaxFyp3TSrlcWBJfu36woGWIvlfSBE61Ce LQO5nE2hbBmqUH4JbLCdHo5LfPISpdCyQ47MlGjWO9tJlcRZDYSZO2bNiw1c6WI5 H+23A98blf4XDBmEoJi2Dfcf1+fuHHXVRkKEGYttqssGS9ltukE+1tHOech7B52t uzTxoK3mkQLaH/KGN6Gks1m+AyOZXUvOMwWmkNEflDdUXNoucllRzvlxXhI95sX0 N1TK3xFgyAvnHOXhS5E6FetaFH4r+i60CLsaNLquAN/gO+/aY0K7DC5Ea2UixiEp /UVj+ETgcQROrhJceokw =K53t -----END PGP SIGNATURE----- --HeFlAV5LIbMFYYuh--