No. When a file is restored, it gets a new inode. A restored file will replace an existing file with the same name, however. So if you are worried about this, just restore into a new, empty directory to avoid any name conflicts.
The dump inode maps are used to keep track of which files were removed after a full dump was done, but before an incremental dump was done. That way when you completely restore a filesystem from a full dump and incrementals, you don't get back all those files that are on the full dump but were removed from the filesystem before the incremental dump was done.
Perhaps a stupid question, but if I restore a dump from a tape/file to a volume on a netapp, and there are inode number conflicts (because the existing volume has a bunch o' files), will the files with duplicate inode numbers be blown away?
Thanks,
Avi
Steve Losen scl@virginia.edu phone: 804-924-0640
University of Virginia ITC Unix Support