From owner-freebsd-stable@FreeBSD.ORG Thu Jan 31 01:49:18 2008 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 D96A116A418; Thu, 31 Jan 2008 01:49:18 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (pool-96-225-216-68.ptldor.fios.verizon.net [96.225.216.68]) by mx1.freebsd.org (Postfix) with ESMTP id 9DBDC13C442; Thu, 31 Jan 2008 01:49:18 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.14.1/8.13.8) with ESMTP id m0V1nIG7009607; Wed, 30 Jan 2008 17:49:18 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.14.1/8.13.4/Submit) with UUCP id m0V1nIcR009603; Wed, 30 Jan 2008 17:49:18 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id BAA04522; Thu, 31 Jan 2008 01:47:04 GMT Message-Id: <200801310147.BAA04522@sopwith.solgatos.com> To: "Steven Hartland" In-reply-to: Your message of "Thu, 31 Jan 2008 01:04:00 GMT." <013201c863a5$2a91a1c0$b6db87d4@multiplay.co.uk> Date: Wed, 30 Jan 2008 17:47:04 +0000 From: Dieter Cc: freebsd-performance@freebsd.org, freebsd-stable@freebsd.org Subject: Re: newfs locks entire machine for 20seconds 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: Thu, 31 Jan 2008 01:49:19 -0000 > > What *exactly* do you mean by > > > >> machine still locks up with no activity for anywhere from 20 to 30 seconds. > > > > Is there disk activity? (e.g. activity light(s) flashing if you have them) > > Cant tell if there is disk activity its in a DC miles away ;) > > > Does top continue to update the screen during the 20-30 seconds? > > > > I'm thinking that newfs has queued up a bunch of disk i/o, and other > > disk i/o gets locked out, but activities that don't require any disk i/o > > (like top, once it is up and running) could continue. Is that what is > > happening? > > No all sessions totally freeze. I have top set to 1 second refreshes and > the clock literally stops and then 20-30 seconds later continues. Wow! > All sessions are via ssh not X if that's of interest. > > I could understand if IO to disk for other processes became slow but > everything including things like top just stop which is quite odd and > concerning. Ok, new idea. Your disk activity is via the network, and your sessions are via the network. Could it be that something network related is saturated?