Re: [deal.II] avoid file system lock when calling P::D::SolutionTransfer::prepare_serialization() ?

2016-06-06 Thread Alberto Sartori
t; option when compiling p4est to use MPI_IO or not. Which version are > you using and how did you configure it? > > On Thu, Jun 2, 2016 at 3:17 PM, Alberto Sartori > > wrote: > > Thanks Bruno, > > > > when I type > > > > (gdb) catch throw >

Re: [deal.II] avoid file system lock when calling P::D::SolutionTransfer::prepare_serialization() ?

2016-06-02 Thread Alberto Sartori
une 2, 2016 at 8:02:15 AM UTC-4, Alberto Sartori wrote: > >> gdb exit with "no stack" so I can't tell the right line of code :( >> > type catch throw in gdb before running your code. > > Best, > > Bruno > -- The deal.II project is locate

Re: [deal.II] avoid file system lock when calling P::D::SolutionTransfer::prepare_serialization() ?

2016-06-02 Thread Alberto Sartori
Dear Wolfgang, thanks for your reply. Indeed the problem occurs when I call p::d::triangulation::save (just after the p::d::SolutionTransfer::prepare_serialization) gdb exit with "no stack" so I can't tell the right line of code :( On Wednesday, June 1, 2016 at 11:32:42 PM UTC+2, banger

[deal.II] avoid file system lock when calling P::D::SolutionTransfer::prepare_serialization() ?

2016-06-01 Thread Alberto Sartori
Hi all, I am running on cluster with LUSTRE file system but it hasn't the 'flock' option turned on. So when I try to save a checkpoint for a future restart I get ``` File locking failed in ADIOI_Set_lock(fd 13,cmd F_SETLKW/7,type F_WRLCK/1,whence 0) with return value and errno 26. - I