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 <[EMAIL PROTECTED]>, 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 - [EMAIL PROTECTED] > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
