If nothing's changed, I believe it is: email to: majordomo@mathworks.com subject: unsubscribe toasters
-----Original Message----- From: Dawn Lovell [mailto:dlovell@centurytel.net] Sent: Friday, October 04, 2002 10:30 AM To: Premanshu Jain Cc: toasters@mathworks.com Subject: Re: ndmpcopy question
I encountered this same message when doing an incremental while migrating to a new filer. The NetApp support person with whom I spoke contacted one of the developers about it. The developer said that the error means that a directory being restored (to the target of the ndmpcopy) referred to an inode which wasn't in the dumpmap.
The process assumes that the directory is correct and that the dumpmap is wrong, so it goes with the directory data instead of the dumpmap. I'm not clear on how that works if the affected file is not in the dump (how is it restored to the target machine?), but I'm undoubtedly missing part of the picture. :-)
He mentioned that the message might be changed to only appear in debug output, since it should not signal anything that would cause data loss. I had started over with a new level 0 and was on a new incremental by the time I found out that info, so I can't comment as to whether the affected files were actually copied by the incremental that generated the message.
Dawn Lovell dlovell@centurytel.net
On Thu, 3 Oct 2002, Premanshu Jain wrote:
While doing level 1 ndmpcopy, i encounter the following error message in
the
log:
nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on
inode
nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on
inode
nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on
inode
nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on
inode
nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on
inode
nacktheknife: LOG: RESTORE: nacktheknife: LOG: Inconsistent dumpmap on
inode
WHAT DOES THIS MEAN ?