Thanks. I tested, and found that it is really a problem with BLCR.
Sincerely,
Zhenxia Zhang
----- Original Message -----
From: "Brian Barrett" <brbarret_at_[hidden]>
To: "General LAM/MPI mailing list" <lam_at_[hidden]>
Sent: Friday, April 21, 2006 1:46 PM
Subject: Re: LAM: lamrestart fails after the execution file renamed
> On Apr 17, 2006, at 7:15 AM, Zhenxia Zhang wrote:
>
> > I rename back the file, the problem is still there.
> > ----------------------------------------------------------------------
> > ----------------
> > $ mv hello2 hello
> > $ lamrestart -ssi cr blcr -ssi cr_blcr_context_file context.mpirun.
> > 1280
> > cri_syscall(CR_OP_RSTRT_REQ, &req): Device or resource busy
> > cri_syscall(CR_OP_RSTRT_REQ, &req): Device or resource busy
>
> Can you use blcr to checkpoint / restart simple non-MPI
> applications? This looks like a problem with BLCR, not MPI (could
> obviously be wrong there), so I'm curious if there isn't some
> fundamental problem.
>
> Brian
>
>
> --
> Brian Barrett
> LAM/MPI developer and all around nice guy
> Have a LAM/MPI day: http://www.lam-mpi.org/
>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
