From owner-freebsd-current@FreeBSD.ORG  Tue Sep  4 15:51:33 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 52FBB16A41B
	for <freebsd-current@freebsd.org>; Tue,  4 Sep 2007 15:51:33 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10])
	by mx1.freebsd.org (Postfix) with ESMTP id 0DE7C13C46C
	for <freebsd-current@freebsd.org>; Tue,  4 Sep 2007 15:51:33 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by cs1.cs.huji.ac.il with esmtp id 1ISagd-000EcK-ME
	for freebsd-current@freebsd.org; Tue, 04 Sep 2007 18:51:31 +0300
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: freebsd-current@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 04 Sep 2007 18:51:31 +0300
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1ISagd-000EcK-ME@cs1.cs.huji.ac.il>
Subject: dump problems
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Sep 2007 15:51:33 -0000

dump start out nicely, but then it justs hangs.
have tried it with different file systems, the output
is also a file, again tried it with different file system.
the only way it works is if the output file is /dev/null (very
fast, but not realy helpful :-)

the host is smp, and iddle.
and just in case, it's running -current from last week.

any insights?

	danny