CFD Online Logo CFD Online URL
Home > Forums > OpenFOAM Running, Solving & CFD

NFS timing problems

Register Blogs Members List Search Today's Posts Mark Forums Read

LinkBack Thread Tools Display Modes
Old   March 25, 2002, 08:35
Default I recently came across an iss
Mattijs Janssens (Mattijs)
Posts: n/a
I recently came across an issue to do with running a case with files on another machine (NFS mounted). If
- runTimeModifiable is on
- the machines have clock skew
- and the iteration lasts shorter than the clock skewI sometimes get a 'FatalError: no read constructor specified for phi'. I traced this to a problem in NFS with mtime on files.

Does anyone have experience with this? Anyone know any solutions?

  Reply With Quote

Old   March 25, 2002, 08:48
Default Yes, we also have this proble
Niklas Nordin (Niklas)
Posts: n/a
Yes, we also have this problem.

I have a quick and dirty solution
I use a script to run the case.
The output, both STDOUT and STDERR, is piped
to a log-file and when the job's done it
looks for the special error message in the log
file and restarts the script if the error message was found. (told you it was dirty)
It works though.

  Reply With Quote

Old   April 8, 2002, 04:47
Default The failsafe method is to swi
Mattijs Janssens (Mattijs)
Posts: n/a
The failsafe method is to switch of runTimeModifiable.

Alternatively you can synchronize your clocks (by a time server).

The whole problem is caused by the caching done by NFS. If the file is still in cache the modification time is that of the local machine; if it is out of cache the modification time is that of the server.

The modification time is used by the database to reread files that have changed at runtime (if runTimeModifiable is swtiched on).
  Reply With Quote

Old   September 30, 2004, 05:23
Default The third way of preventing t
Mattijs Janssens (Mattijs)
Posts: n/a
The third way of preventing this error ('FatalError: no read constructor specified') is to allow for some difference in timing. This is done with the


parameter in the ~/.foam2.3/controlDict file. Set it to a value larger than the timing difference between the machines.

So there are three solutions to the problem. In order of (my) preference:
- synchronize the times on your machines. (Foam is not the only program that will give problems if the times are not synchronized)
- increase the 'slack' using above fileModificationSkew
if the time difference is not execessively large
- switch off runTimeModifiable in the controlDict
  Reply With Quote


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
Ignition timing for diesel combustion Ankur Siemens 5 March 15, 2008 21:18
Timing bench mark Michele FLUENT 1 May 15, 2006 11:45
Snap Timing in KIVA Felix Main CFD Forum 3 March 17, 2006 03:31
Heat Release and Ignition Timing in KIVA Felix Tae Main CFD Forum 0 January 25, 2006 02:08
Injections at Different Timing Nicole FLUENT 1 July 10, 2002 14:20

All times are GMT -4. The time now is 11:07.