From owner-freebsd-current@FreeBSD.ORG  Tue Sep  4 18:47:17 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 5E31016A417
	for <freebsd-current@FreeBSD.org>; Tue,  4 Sep 2007 18:47:17 +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 18D0613C45D
	for <freebsd-current@FreeBSD.org>; Tue,  4 Sep 2007 18:47:17 +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 1ISdQi-000GkC-4v; Tue, 04 Sep 2007 21:47:16 +0300
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: Gavin Atkinson <gavin@FreeBSD.org>
In-reply-to: Your message of Tue, 04 Sep 2007 17:24:32 +0100 .
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 04 Sep 2007 21:47:16 +0300
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1ISdQi-000GkC-4v@cs1.cs.huji.ac.il>
Cc: freebsd-current@FreeBSD.org
Subject: Re: 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 18:47:17 -0000

> On Tue, 2007-09-04 at 18:51 +0300, Danny Braniss wrote:
> > 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 :-)
> 
> When it hangs, what is printed when you send it a CTRL-T?
> 
off the top of my head:

... running ...

it seems to be a problem on the writing side, since setting the output
to /dev/null actually works.

the commands used were:

dump 0Lf - /some/file/system | restore rf -
this got stuck, so I started experimenting:
dump 0Lf file.dump  /some/file/system

gets stuck, ^T will mostly return ... [running] ... since at least
one of the dump process is running, but my guess it's just monitoring.
I also tried without the L flag, but did not change the result.
the only dump that finishes, is when the output is /dev/null.

danny