From owner-freebsd-stable@FreeBSD.ORG Mon Oct 19 11:55:16 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9960106566C for ; Mon, 19 Oct 2009 11:55:16 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9FAF18FC12 for ; Mon, 19 Oct 2009 11:55:16 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1MzqpK-0002mC-R9 for freebsd-stable@freebsd.org; Mon, 19 Oct 2009 13:55:02 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 19 Oct 2009 13:55:02 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 19 Oct 2009 13:55:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Mon, 19 Oct 2009 13:50:50 +0200 Lines: 18 Message-ID: References: <9bbcef730910130633w150571a0k461fb4e67a51fb1d@mail.gmail.com> <9bbcef730910131057i71db846et1f0d4aeadef5e302@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.23 (X11/20090928) In-Reply-To: Sender: news Subject: Re: Extreme console latency during disk IO (8.0-RC1, previous releases also affected according to others) 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: Mon, 19 Oct 2009 11:55:17 -0000 Ivan Voras wrote: > Another data point - the OS in the VM in question hanged today sometime > after 5 AM in the following way: > > * console nonresponsive (also to ctrl-alt-del) > * ssh login nonresponsive (timeout) > * ping works (!) > > Judging by the last seen timestamp, the machine should have been in the > process of receiving rsync backups - so IO-bound. It looks like something really could be fishy in this area, at least with VMWare. The same thing happened again, and I have an additional data point: I left 'top' running on the console and when I attached the VMWare console to the VM, the top was still running ok, but as soon as I hit a key on the keyboard, the OS console locked up. All other symptoms were as I enumerated above.