From owner-freebsd-current@FreeBSD.ORG  Mon May 12 13:15:39 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 6694937B421
	for <freebsd-current@freebsd.org>;
	Mon, 12 May 2003 13:15:39 -0700 (PDT)
Received: from mail.imp.ch (mail.imp.ch [157.161.1.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2086243F85
	for <freebsd-current@freebsd.org>;
	Mon, 12 May 2003 13:15:38 -0700 (PDT)	(envelope-from mb@imp.ch)
Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9])
	by mail.imp.ch (8.12.6p2/8.12.3) with ESMTP id h4CKFZPq097885;
	Mon, 12 May 2003 22:15:36 +0200 (CEST)
	(envelope-from Martin.Blapp@imp.ch)
Date: Mon, 12 May 2003 22:15:35 +0200 (CEST)
From: Martin Blapp <mb@imp.ch>
To: Lukas Ertl <l.ertl@univie.ac.at>
In-Reply-To: <20030512215835.V600@korben.in.tern>
Message-ID: <20030512221444.R47986@cvs.imp.ch>
References: <20030512215835.V600@korben.in.tern>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: Dump(8) hosed on CURRENT
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Mon, 12 May 2003 20:15:39 -0000


Hi,

> I now did a test with dump -L on a live filesystem, and I've seen the
> "file expected but not found" error, too. There's obviously something
> broken, we should check if it's related to -L or if it happens always.

I just tested it without "-L" on a live, but not active filesystem.
The restore finishes fine and everything seems to be there.

So dump -L is broken :-(

Martin