From owner-freebsd-stable@FreeBSD.ORG Mon Jun 20 16:30:06 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E16A516A41C; Mon, 20 Jun 2005 16:30:06 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id A290643D58; Mon, 20 Jun 2005 16:30:06 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from ranger.anduin.net ([81.0.162.52] helo=[192.168.1.110]) by anduin.net with esmtpa (Exim 4.50 (FreeBSD)) id 1DkP9x-000DnP-BD; Mon, 20 Jun 2005 18:30:05 +0200 In-Reply-To: <20050620151854.GA41619@stack.nl> References: <20050620151854.GA41619@stack.nl> Mime-Version: 1.0 (Apple Message framework v730) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: =?ISO-8859-1?Q?Eirik_=D8verby?= Date: Mon, 20 Jun 2005 18:29:31 +0200 To: Marc Olzheim X-Mailer: Apple Mail (2.730) Cc: stable@freebsd.org, Robert Watson Subject: Re: NFS-related hang in 5.4? 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, 20 Jun 2005 16:30:07 -0000 On 20. jun. 2005, at 17.18, Marc Olzheim wrote: > On Mon, Jun 20, 2005 at 10:53:19AM +0200, Eirik verby wrote: > >> I know enough not to call this a "confirmation", but disabling >> dummynet did indeed allow me to finish the backup. I never made it >> past 15GBs before, now the full 19GB tar.gz file is done, and the >> boxes are both still running. The funny thing is - I only disabled >> dummynet on one of the boxes now - the source of the backup, the box >> that pushes data. The other box has pretty much 100% the same setup, >> and is also i386. But as traffic shaping can only happen on outgoing >> packets, I suppose that makes sense. >> > > Hmm, does that solve kern/79208 for you as well by any chance ? Seems not. Now, how do I get my box back to life? ;) /Eirik > > Marc >