Dear serge, You are right, I am using the checkpoint_self.c in Documentation/checkpoint dir. Now, I am using the self_checkpoint in user-cr, but it still has some errors: some content in image file: "f_op lacks checkpoint^@^O'^@^@^H^@^@^@^D^@^@^@<^@^@^@^@pid 4375 ts k self_checkpoint err -9]: files_struct" In fact, when checkpoint externally, it also has the error message mentioned above. I traced there is an error in freezer_checkpointing(external checkpointing), can you point out me where might be wrong? Jefera On Mon, Jun 7, 2010 at 10:27 AM, Jerf gefera <jgefera@xxxxxxxxx> wrote: > Hi all, > I am using CKPT V19, when I tried to test the checkpoint, there was a > error: > 1) using checkpoint_self, error message is: "not container initckpt: > Invalid argument", FAILED; > 2) using external checkpoint, there are two situations, if I did it like > this > a) > $ ./test & > [1] 3493 > $ echo 3493 > /cgroup/0/tasks" --------------------> FAILED, error message > is "echo: write error: Device or resource busy" > b) > $ ./loop & > $./checkpoint 3493 >loop.ckpt --------------------->FAILED, error > message is > "checkpoint: Device or resource busy > (you may use 'ckptinfo -e' for more info)" > > I do not know what is wrong, > Thank you very much.. > Jefera > _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
