On Wed, Apr 06, 2016 at 07:16:23PM +0200, Jean-Pierre André wrote: > Richard W.M. Jones wrote: > >The problem is not this particular disk image. The problem is that > >when we use virt-v2v to convert 1000s of Windows guests we don't want > >to hit this problem with some guest. virt-v2v examines a few files in > >\Windows\system32, but when it hits a guest like this one it will die, > >even though the corrupt name has nothing to do with any file that > >virt-v2v cares about nor is trying to open. > > What is your need ?
Looking at the v2v code, I think the only thing we do is to read through the directory a couple of times. We're looking for 'config' and 'drivers', to find the registry and drivers subdirs respectively. I guess this kind of corruption could happen in any directory, it just happens to be %systemroot% in this particular instance. > If you need to access some specific files, and to not > crash on reading directories, you can use Erik's proposal. I looked at that and it looks ideal. If we really needed to open/delete/link to a file that had a corrupt name, then it would be fair enough for virt-v2v to stop. Thanks, Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html ------------------------------------------------------------------------------ _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
