Thanks to everyone who replied to my question regarding ndmpcopy versus vol copy when migrating from a F740 to a F820! Based on the recommendations, we've done a level 0 ndmpcopy and two increasing incrementals (level 1 and level 2). On what was to be our last incremental (level 3) with the source filesystem read-only, we received the following message:
newfiler: LOG: RESTORE: newfiler: LOG: Inconsistent dumpmap on inode 10831660.
The copy goes on to complete successfully, but I'm concerned about the impact of this. I'm running a find to try to locate the file or directory with that inode, but it's going to run forever with the number of files we have. Is there a faster way than find to match the inode to a file?
Does anyone know if this is a serious error? I'd thought that it was probably the result of a file on the target filesystem being changed outside of the ndmpcopy process. That shouldn't have happened, but it's certainly possible. I called NetApp support about this, however, and was told that it was a filesystem problem on the target filer and that we should bring it down and run wafl_check.
I can't find the error in the archives or on the NOW site, so I would greatly appreciate any insight. Thanks for your time!
Dawn Lovell dlovell@centurytel.net