From owner-freebsd-current@FreeBSD.ORG Sat Jul 13 05:42:26 2013 Return-Path: Delivered-To: freebsd-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 2FB21F56; Sat, 13 Jul 2013 05:42:26 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 997F111CA; Sat, 13 Jul 2013 05:42:25 +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 r6D5gKZi072119; Sat, 13 Jul 2013 08:42:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r6D5gKZi072119 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r6D5gKhE072118; Sat, 13 Jul 2013 08:42:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 13 Jul 2013 08:42:20 +0300 From: Konstantin Belousov To: Ian FREISLICH Subject: Re: Filesystem wedges caused by r251446 Message-ID: <20130713054220.GJ91021@kib.kiev.ua> References: <20130712201051.GI91021@kib.kiev.ua> <201307110923.06548.jhb@freebsd.org> <201307091202.24493.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="D1DlOxT2xGoS+WIB" Content-Disposition: inline In-Reply-To: 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-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: Sat, 13 Jul 2013 05:42:26 -0000 --D1DlOxT2xGoS+WIB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jul 12, 2013 at 11:34:18PM +0200, Ian FREISLICH wrote: > (kgdb) print runningbufreq > $1 = 1 > (kgdb) print runningbufspace > $2 = 0 > (kgdb) print lorunningspace > $3 = 4587520 > (kgdb) print hirunningspace > $4 = 4194304 This is extremely weird. The hirunningspace is less then lorunningspace, am I right ? This causes the runningbufspace machinery to never wake up waiters, I believe. The process is put on sleep when hirunningspace is reached, but would be woken up after we cross lorunningspace. If the space never goes up to your bigger lorunningspace, you get the process stuck forever, owning vnode lock and making machine inoperable. I just verified on the 4G VM on amd64, my numbers for lo is 4587520, for high 6881280. Verify your tuning and kernel options, which you should have provided with the original report, I think. --D1DlOxT2xGoS+WIB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJR4Oi7AAoJEJDCuSvBvK1BoyEP/iAMyHlwFAvxY8eeDWmgOCZH 76F5LMvoEnECUHm/tCgFdp9fArULIsAab9go+WQ+xn0CQ1ybFRM6ow0m6wehxIRl 0wySu2jDOhhY0zSYS8O0Ereo4Rk1FHce1uw0a5JhPpj8WfSElJsF/zMZ6AvEvZ0w sbTbIyyZNzDIk76G9HWKpLye78zn1SFVxnnzHLXe3VrkpTnCdV+zJT97v9i76wzD +YduVPmZTSOTSGYsGlMsxqJW79YTw7WEI7TYhbQPDqUKMNIEMTUZHRn2pbr/ioMc /QZR4/G7THc4zGP3H2/KrRBCncvrXf+z6TyWkSsqj06dX1VkDXyIpTFHs6krFKcn KzHbXDpZ+RxvC1jifIgfvbG3TtGxrGe2VbMFJ5hfuXyCmojBL9wz1WLtyACPlgd4 hdMsReP7/TtB26zSJZoI/ow6fzsjbQd2wz6qvl5e+JFoMM7i0x2ep+IraP43M2oc OEzvVXZRf9w+VI9gzglhvhfUu5+lM1nqwtm24uzv/bukZpiVRPHDQhvQo6iVxoPj XNXkAY8s+VwbT6Ohnp4laTk+A248Udv4ZFAC+HuPWrooIIF2SfifMqvCK98UxMd2 1n9rufckXhH87q1nW5hHnkNB9aBpWYX0TlJHdEMnUwsX0KfE0iv6Y7IMynux8xV8 clf8AgXVtOvJuA9ja3u1 =bA8l -----END PGP SIGNATURE----- --D1DlOxT2xGoS+WIB--