From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 18:18:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9360A16A4CE; Mon, 8 Mar 2004 18:18:26 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84AE043D4C; Mon, 8 Mar 2004 18:18:26 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 7530572DCB; Mon, 8 Mar 2004 18:18:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 6FE1F72DB5; Mon, 8 Mar 2004 18:18:26 -0800 (PST) Date: Mon, 8 Mar 2004 18:18:26 -0800 (PST) From: Doug White To: Lukas Ertl In-Reply-To: <20040306191501.F919@korben.in.tern> Message-ID: <20040308181205.G63095@carver.gumbysoft.com> References: <20040306191501.F919@korben.in.tern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@FreeBSD.org Subject: Re: dump(8) deadlock (ULE bug?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 09 Mar 2004 02:18:26 -0000 On Sat, 6 Mar 2004, Lukas Ertl wrote: > Hi, > > I have this filesystem: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1g 16244334 992310 13952478 7% > > and I'm trying to dump it like: > > dump -0uf - /dev/da0s1g > news.dump $PWD isn't on /devad0s1g, is it? > The problem is that dump(8) seems to run into a deadlock or race in Pass > IV [regular files], because then the dump procs all go into state "paused" > and don't do anything anymore. > > 1080 root 20 0 2116K 1664K pause 0 0:04 0.00% 0.00% dump > 1082 root 20 0 2116K 1664K pause 3 0:04 0.00% 0.00% dump > 1081 root 20 0 2116K 1664K pause 2 0:04 0.00% 0.00% dump > 1079 root 4 0 2244K 1704K sbwait 3 0:03 0.00% 0.00% dump pause means the process has called pause(3) and is waiting for a signal. Considering the parent is in sbwait, which is a network send, it appears to be waiting for network I/O. Why it would be doing network I/O, I don't know; I'd suggest tcpdump and/or ktrace. I don't know if dump is SIGIO based or not. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org