Hello, I have a new filer running 7.2.2. I am using ndmpcopy from the command line of the new filer to copy a directory (not a whole volume) from an old filer running 7.1.1.1. Many of the directories I am moving are fine, but at least one (so far) has produced some errors while the ndmpcopy was running:
Ndmpcopy: cfs1: Log: RESTORE: File creation failed: ...(258720)
The ndmpcopy runs and finishes without error. The ndmpdcopy of one of these directories had 179 of these failures.
Ndmpcopy: old: Log: DUMP: 124480831 KB Ndmpcopy: new: Log: RESTORE: RESTORE IS DONE Ndmpcopy: new:newcfs1: Notify: restore successful Ndmpcopy: old: Log: DUMP: DUMP IS DONE Ndmpcopy: old: Log: DUMP: Deleting "/vol/vol1/../snapshot_for_backup.234" snapshot.
I then turned on ndmpd debug to 70 and ran it again. This time each of the failed files had a similar segment of errors like this:
Jul 11 15:56:09 EDT [ndmpd:10]: Message NDMP_LOG_MESSAGE sent Jul 11 15:56:09 EDT [ndmpd:10]: Message Header: Jul 11 15:56:09 EDT [ndmpd:10]: Sequence 22 Jul 11 15:56:09 EDT [ndmpd:10]: Timestamp 1184183769 Jul 11 15:56:09 EDT [ndmpd:10]: Msgtype 0 Jul 11 15:56:09 EDT [ndmpd:10]: Method 1539 Jul 11 15:56:09 EDT [ndmpd:10]: ReplySequence 0 Jul 11 15:56:09 EDT [ndmpd:10]: Error NDMP_NO_ERR Jul 11 15:56:09 EDT [ndmpd:10]: Log type: 0 Jul 11 15:56:09 EDT [ndmpd:10]: Message id: 0 Jul 11 15:56:09 EDT [ndmpd:10]: Log message: RESTORE: File creation failed: ...(258729) Ndmpcopy: new: Log: RESTORE: File creation failed: ...(258729)
The new filer is empty and the destination volume is a big flexvol. The source directory (qtree) is in a traditional volume.
I have opened a case, but nothing back yet. Anyone ever see this before ?
Thanks, Paul
This could be one of two things:
1. You ran out of inodes (doubtful) 2. You hit your Maximum Directory size.
Not sure what the default DIR size is anymore, but here is how you check both:
1. df -i -> check inode usage. Just for kicks, check the source and destination 2. vol status -v -> look for dirsize. See if on the destination it comes close to the number you listed: 258729
If you need to increase the inodes, use the "maxfiles" command If you need to adjust the MAXDIRSIZE, use the vol options command.
On 7/12/07, Paul Letta letta@jlab.org wrote:
Hello, I have a new filer running 7.2.2. I am using ndmpcopy from the command line of the new filer to copy a directory (not a whole volume) from an old filer running 7.1.1.1. Many of the directories I am moving are fine, but at least one (so far) has produced some errors while the ndmpcopy was running:
Ndmpcopy: cfs1: Log: RESTORE: File creation failed: ...(258720)
The ndmpcopy runs and finishes without error. The ndmpdcopy of one of these directories had 179 of these failures.
Ndmpcopy: old: Log: DUMP: 124480831 KB Ndmpcopy: new: Log: RESTORE: RESTORE IS DONE Ndmpcopy: new:newcfs1: Notify: restore successful Ndmpcopy: old: Log: DUMP: DUMP IS DONE Ndmpcopy: old: Log: DUMP: Deleting "/vol/vol1/../snapshot_for_backup.234" snapshot.
I then turned on ndmpd debug to 70 and ran it again. This time each of the failed files had a similar segment of errors like this:
Jul 11 15:56:09 EDT [ndmpd:10]: Message NDMP_LOG_MESSAGE sent Jul 11 15:56:09 EDT [ndmpd:10]: Message Header: Jul 11 15:56:09 EDT [ndmpd:10]: Sequence 22 Jul 11 15:56:09 EDT [ndmpd:10]: Timestamp 1184183769 Jul 11 15:56:09 EDT [ndmpd:10]: Msgtype 0 Jul 11 15:56:09 EDT [ndmpd:10]: Method 1539 Jul 11 15:56:09 EDT [ndmpd:10]: ReplySequence 0 Jul 11 15:56:09 EDT [ndmpd:10]: Error NDMP_NO_ERR Jul 11 15:56:09 EDT [ndmpd:10]: Log type: 0 Jul 11 15:56:09 EDT [ndmpd:10]: Message id: 0 Jul 11 15:56:09 EDT [ndmpd:10]: Log message: RESTORE: File creation failed: ...(258729) Ndmpcopy: new: Log: RESTORE: File creation failed: ...(258729)
The new filer is empty and the destination volume is a big flexvol. The source directory (qtree) is in a traditional volume.
I have opened a case, but nothing back yet. Anyone ever see this before ?
Thanks, Paul
-
Paul Letta -
tmac