[Devel] Re: Problem: Device or resource busy
Serge E. Hallyn
serge at hallyn.com
Fri Jun 11 15:52:38 PDT 2010
Quoting Jerf gefera (jgefera at gmail.com):
> 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
As Matt asked in another thread, are you still using v19?
v21 should iirc tell you the name of the file causing the trouble. If
v21 is not an option, then pls modify your external checkpoint script
to keep the task frozen, then look at the contents of /proc/pid/fd
and /proc/pid/fdinfo for the checkpointed pid. Something like
pid=$1
touch outout
/bin/ls /proc/$pid/fd >> outout
/bin/ls /proc/$pid/fdinfo >> outout
for f in `/bin/ls /proc/$pid/fdinfo`; do
echo "/proc/$pid/fdinfo/$f:" >> outout
/bin/ls /proc/$pid/fdinfo/$f >> outout
done
for f in `/bin/ls /proc/$pid/fd`; do
echo "/proc/$pid/fd/$f:" >> outout
stat /proc/$pid/fd/$f >> outout
done
Really, I'm assuming that the problem is either an inherited open fd to
your pty, or an inherited nscd socket. But let's see.
-serge
_______________________________________________
Containers mailing list
Containers at lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
More information about the Devel
mailing list