On Thu, 25 Oct 2001, Steve Losen wrote:
I wouldn't worry about this error too much and I highly doubt that your new volume is corrupt and needs a wafl_check. You didn't say what version of ONTAP you are using, but I can tell you from my own personal experience that incremental restore has a long history of bugginess. I would bet that this error is just restore weirdness and not a filesystem problem. Still, it wouldn't hurt to find the file mentioned in the error message and verify that it was copied.
Thanks for your help! I don't know to which filer the inode belonged, but my endless find was running on the source. I should have mentioned that we're running 5.3.6R2 on the source filer and 6.1.1R1 on the target filer.
I called back into tech support regarding the error; it turns out that my call was originally logged as a block inconsistency instead of the ndmpcopy inconsistent dumpmap error. I just received a very helpful message that basically said that it would be safe to ignore the inconsistent dumpmap message.
It was evidently a result of the dumpmap and the actual directory structure disagreeing, i.e., a file existed in the directory that the dumpmap didn't show. The process goes with what the directory has, so the message is more of a FYI than an error. I'm very loosely paraphrasing here, since I don't want to post someone's email without their permission. Please don't blame NetApp for any misstatements I make.
Thanks to everyone for their assistance! This list and its archives are such helpful resources. I particularly enjoyed the faceplate color discussion, especially after seeing the truly unique shade of green on the 820s. :-)
Dawn Lovell dlovell@centurytel.net