Re: [Dump-users] Expected next file xxxx, got yyyy

[Stelian P. <st...@po...>]

Le mercredi 12 mars 2008 à 11:57 -0700, Kenneth Porter a écrit :
> When comparing, this is treated as a compare error, and counted against the 
> error limit. The comments in the code suggest that this isn't an error:
> 
>                 /*
>                  * If we find files on the tape that have no corresponding
>                  * directory entries, then we must have found a file that
>                  * was created while the dump was in progress. Since we have
>                  * no name for it, we discard it knowing that it will be
>                  * on the next incremental tape.
>                  */
>                 if (first != curfile.ino) {
>                         fprintf(stderr, "expected next file %ld, got %lu\n",
>                                 (long)first, (unsigned long)curfile.ino);
>                         do_compare_error;
>                         skipfile();
>                         goto next;
>                 }
> 
> Is there a reason to treat this as a hard error? I'd suggest removing the 
> do_compare_error.

Seems reasonable indeed...

-- 
Stelian Pop <st...@po...>