Succes story. I modified a checkpoint part of the openvz 2.6.32 kernel (cpt_mm.c) which handles a vma areas by replacing vma->vm_file with vma->vm_prfile if vma->prfile != 0. After that a checkpoint-restore is performed without any error. I think that CRIU utils must know about that field in the vma struct (if there is that filed) before CRIU can suspend a container located inside an aufs file system. Another solution may be to use vma_ops in aufs and to keep vma->vm_file unchanged, -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
