From owner-freebsd-fs@FreeBSD.ORG Thu Aug 22 16:03:19 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EAB48306; Thu, 22 Aug 2013 16:03:19 +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 4401D27B7; Thu, 22 Aug 2013 16:03:19 +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 r7MG3Ean028767; Thu, 22 Aug 2013 19:03:14 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r7MG3Ean028767 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r7MG3Exn028766; Thu, 22 Aug 2013 19:03:14 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 22 Aug 2013 19:03:14 +0300 From: Konstantin Belousov To: Edward Tomasz Napiera?a Subject: Re: 9.2-RC1: LORs / Deadlock with SU+J on HAST in "memsync" mode Message-ID: <20130822160314.GS4972@kib.kiev.ua> References: <20130819115101.ae9c0cf788f881dc4de464c5@yamagi.org> <20130822102121.a799b116b0f6b0f7c90ba578@yamagi.org> <20130822093138.GO4972@kib.kiev.ua> <23FCE234-E811-4160-BCDD-B0E2B832DCD3@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="E5JQ0pcKq0ha6n5z" Content-Disposition: inline In-Reply-To: <23FCE234-E811-4160-BCDD-B0E2B832DCD3@FreeBSD.org> 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: 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: Thu, 22 Aug 2013 16:03:20 -0000 --E5JQ0pcKq0ha6n5z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 22, 2013 at 02:41:19PM +0200, Edward Tomasz Napiera?a wrote: > Wiadomo?? napisana przez Konstantin Belousov w dniu 22 sie 2013, o godz. = 11:31: > > This has absolutely nothing to do with the deadlock we trying to catch. > > On your case, it seems that all i/o on the box is stalled, and my guess > > is that hastd just recursed waiting for some i/o completion which requi= res > > working hastd to finish. > >=20 > > Talk to hastd author(s) about this. >=20 > Isn't this just another case of deadlock caused by being out of bufs? Well, this is indeed yet another case of the producer of the free resource (pbufs) requiring the same resource to proceed. Or, where the system should get more buffers ? --E5JQ0pcKq0ha6n5z Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iQIcBAEBAgAGBQJSFjZBAAoJEJDCuSvBvK1Bhb0QAIgR9BKukQgxO+uuJL657xKq p/eTcEkLX+JaSUMLlChZpO+NYCoYrvKxUEbrrkl7w+ctPMtl1uddaKBEi9m+fJD1 SVr+ANPzC1EAtjJYUOf8RHJSMRr8AAmSWclBMR4Ds/isN68DK11JCrbDKxUHw5cg nF6RgGrIK2wR8Srnc/qe+RXgti/4rrjrTKYdNz6OT+aP9S/XueCWTG5AtaVxumt6 3xAMj4Ic6YviRpFhMuIhmdjICIuTVy80c3b7XmxY3VB7j3s4JSsrWIfFk67Rzy53 g821mxNtpVCa74w4aPT2tPFP925UUNORE4gtJdgj0sBdaIXDWyO3lzohQsUGwRGo 78FEGagPsM2VMWK5iF0b+8AwS7NRPIA2gw93Opq+iV6lNj+jdhTBB1FqdBBlqfbC zDMG4gpb4U1OgPmpQQNehkh6tWK//PJVTCKVHFT+7kOKCsYo7796BKR8tBPwJXr0 NPO2l01feVFbfQj3uPS2lg+Z5r3TJGfhiyycvvOSnyY4/jsGggskaqhNsa/WFaSz Aego5IJV4nuFcrRDX996fdkPVR05aea+xD0OjVEBxRGIltbkGK6t/xhvwwTy2L9D /boPmQuCpZG0g+dUnV4FKBXJ3pRIC5fcTtLi+8QkEfEF6ddxeZMVcqputC2cSrT8 4Ibo58BZdsXd6hdpr7F2 =zneU -----END PGP SIGNATURE----- --E5JQ0pcKq0ha6n5z--