From owner-freebsd-current Thu Jan 9 8:37:47 2003 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 C5FBB37B405; Thu, 9 Jan 2003 08:37:45 -0800 (PST) Received: from critter.freebsd.dk (esplanaden.cybercity.dk [212.242.40.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C8B543F18; Thu, 9 Jan 2003 08:37:45 -0800 (PST) (envelope-from phk@freebsd.org) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id h09GbWOH015149; Thu, 9 Jan 2003 17:37:33 +0100 (CET) (envelope-from phk@freebsd.org) To: Dag-Erling Smorgrav Cc: current@freebsd.org, mckusick@freebsd.org Subject: Re: strange dump/restore behaviour From: phk@freebsd.org In-Reply-To: Your message of "Thu, 09 Jan 2003 16:41:10 +0100." Date: Thu, 09 Jan 2003 17:37:32 +0100 Message-ID: <15148.1042130252@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've seen this when dumping live filesystems. I belive it means that dump couldn't find the file it had already dumped in the directory once it got to dump the contents. In message , Dag-Erling Smorgrav writes: >This happened while copying data over to a new disk (mounted on /mnt >and /mnt/usr; the original disk has only one partition). The machine >was in single-user mode, but / was mounted read-write due to restore's >insistance on placing temporary files in /tmp (I found out later that >it respects TMPDIR, though the man page doesn't mention it). > >root@dsa /mnt# dump -0Laf- / | restore -rf- > DUMP: Date of this level 0 dump: Thu Jan 9 16:11:42 2003 > DUMP: Date of last level 0 dump: the epoch > DUMP: Dumping snapshot of /dev/da0a (/) to standard output > DUMP: mapping (Pass I) [regular files] > DUMP: mapping (Pass II) [directories] > DUMP: estimated 1838856 tape blocks. > DUMP: dumping (Pass III) [directories] > DUMP: dumping (Pass IV) [regular files] >warning: ./usr: File exists >expected next file 4, got 3 >[...] > >I can imagine that the file that caused the warning message was one of >restore's temporary files, but a) I've never seen this before, and b) >isn't -L supposed to prevent just that? > >DES >-- >Dag-Erling Smorgrav - des@ofug.org > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message