Jason Parker-Burlingham wrote:
> Mandy Kirkconnell <alkirkco@xxxxxxx> writes:
>
>>I agree that it looks like there are a bunch of null filename
>>strings.
>
> I thought of this, too.
>
>>Jason, you mentioned that the point of error doesn't seem to be
>>consistent but it sounds like it's reproducible in the sense that
>>you've seen this behaviour more than once.
>
>
> Happens every time I pipe xfsdump into xfsrestore.
Do you mean ONLY when the data is piped? Have you tried dumping to a
file then restoring the file (ie. -f /tmp/dumpfile)? The dump file
could get quite big depending on the size of your filesystem but it
might be a good thing to test. It may even narrow this down to either
the dump or the restore. I'm wondering if piping the data is causing
the problem to _appear_ in xfsrestore but the problem may actually be in
the dump.
> I'm more than happy to run commands and send you output as required:
> the whole thing is giving me the willies.
As Tim suggested, turning on debugging would be helpful. If your
filesystem is reasonably small you can use the -v option to increase
verbosity to -v3, -v4 or even -v5 but this may be a lot of output. I
guess I would start with the -v on the xfsrestore command for now. If
it looks like xfsrestore is reading in null strings from stdin then
we'll probably want to take a look at the xfsdump debugging as well.
Mandy
|