From owner-freebsd-current@FreeBSD.ORG Sat Mar 6 10:15:46 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 9245616A4CE for ; Sat, 6 Mar 2004 10:15:46 -0800 (PST) Received: from mailbox.univie.ac.at (mailbox.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E72D443D46 for ; Sat, 6 Mar 2004 10:15:45 -0800 (PST) (envelope-from le@FreeBSD.org) Received: from wireless (adslle.cc.univie.ac.at [131.130.102.11]) i26IFdhX1110166 for ; Sat, 6 Mar 2004 19:15:41 +0100 Date: Sat, 6 Mar 2004 19:15:39 +0100 (CET) From: Lukas Ertl To: current@FreeBSD.org Message-ID: <20040306191501.F919@korben.in.tern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DCC-ZID-Univie-Metrics: mailbox 4251; Body=1 Fuz1=1 Fuz2=1 Subject: 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: Sat, 06 Mar 2004 18:15:46 -0000 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 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 If I run dump subsequently, the deadlock happens at different times, as I get different output files until I have to cancel the dump: -rw-r--r-- 1 root news 239790080 Mar 6 18:56 news.dump.1 -rw-r--r-- 1 root news 20848640 Mar 6 18:56 news.dump.2 -rw-r--r-- 1 root news 302807040 Mar 6 18:57 news.dump.3 -rw-r--r-- 1 root news 114903040 Mar 6 19:00 news.dump.4 -rw-r--r-- 1 root news 353925120 Mar 6 19:01 news.dump.5 -rw-r--r-- 1 root news 55582720 Mar 6 19:02 news.dump.6 -rw-r--r-- 1 root news 418723840 Mar 6 19:03 news.dump.7 -rw-r--r-- 1 root news 89896960 Mar 6 19:04 news.dump.8 -rw-r--r-- 1 root news 248770560 Mar 6 19:06 news.dump.9 Could this be a possible ULE bug? This is a kernel from Mon Mar 1 16:19:21 CET 2004, on a dual P4 Xeon with Hyperthreading enabled. regards, le -- Lukas Ertl http://mailbox.univie.ac.at/~le/ le@FreeBSD.org http://people.freebsd.org/~le/