xfsrestore: incorrect restore if file becomes a dir

[David Brown <davidb@xxxxxxxxxx>]

http://oss.sgi.com/bugzilla/show_bug.cgi?id=915

I've had this happen again.  It appears to be the case if between
incremental dumps, a file is deleted and a directory is created that
gets the same inode number.  The restore leaves a file in place of the
directory.  If the new directory has any contents, xfsrestore prints a
warning, and doesn't restore the subdirectory contents.

Given the sparseness of inodes, this doesn't seem to occur all that
frequently, but I do have a couple of backups that exhibit the
behavior.  If no one has any ideas, I'll start digging through
xfsrestore to see if I can figure out what is happening.

Thanks,
David Brown