Mandy Kirkconnell <alkirkco@xxxxxxx> writes:
> Nathan Scott wrote:
>> Don't think so, looks like a bug. Almost looks like the filename
>> string is null for some reason, somewhere in restore (those mkdir
>> errors, etc, above - look like they're trying to print filenames).
>>
>> Does this ring any bells Mandy?
>
> No, this is new to me.
Uh-oh.
> 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.
> Is there anything unique or special about the data you're restoring?
It's on an lvm1 logical volume; there's only one physical volume in
the group. I was trying to dump from an LVM snapshot, but I just
tried
$ sudo xfsdump -l0 -J - /home | sudo xfsrestore -J -t -
and soon started seeing output like
//mail/humbug/
/.samba-profile//
//build/Class-Accessor-0.17//
///
///
> It looks like the FS may have extended attributes (non-root, secure,
> or both ??).
I'm not sure. I don't believe I've set any myself. How can I tell
for sure? (I looked briefly at the attr(1) manpage but didn't find it
helpful. getfattr(1) doesn't reveal anything except for
user.SGI_XFSDUMP_SKIP_FILE on temp directory (yes, it doesn't work; I
know). How can I list root extended attributes?
> I haven't been able to repro this yet so any additional info would
> be helpful.
I'm more than happy to run commands and send you output as required:
the whole thing is giving me the willies.
jason
--
http://panix.com/~jasonp?BabyPictures
|