On Mon, Jun 07, 2010 at 10:27:08AM +0900, Jerf gefera wrote: > Hi all, > I am using CKPT V19, when I tried to test the checkpoint, there was a error: Hi, Note: We're up to v21 now. > 1) using checkpoint_self, error message is: "not container initckpt: Invalid > argument", FAILED; Hmm, I don't recognize this error message and it doesn't seem to be in v19 -- I checked under checkpoint/, Documentation/checkpoint/, and even in user-cr v19. Where'd you get it or where's the code? > 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" Chances are you are hitting the following limitation: you can't move a task from or to a frozen cgroup. What does /cgroup/0/tasks/freezer.state show? The following will show the freezer state if the tasks current cgroup (bash shell fragment): FILE="/cgroup$(grep freezer /proc/3493/cgroup | head -n 1 | cut -d : -f 3)/freezer.state" if [ '!' -e "${FILE}" ]; then echo THAWED # Can't freeze without a freezer.state file else cat "${FILE}" fi Also, just in case it's useful, what mount options were used for this cgroup mount? > b) > $ ./loop & > $./checkpoint 3493 >loop.ckpt --------------------->FAILED, error message > is > "checkpoint: Device or resource busy > (you may use 'ckptinfo -e' for more info)" What does ckptinfo -e show? Do you have CHECKPOINT_DEBUG configured? What's dmesg output look like? These pieces of information will usually show what returned EBUSY. You can also supply the -l [logfile] arguments to checkpoint to log the error information. No matter what, I recommend recompiling with CHECKPOINT_DEBUG enabled. Then add ckpt_debug=0xffff to your kernel boot line in grub/<your bootloader>. Cheers, -Matt Helsley _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers