This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Malte, In the last response, wherever I wrote "ifort" I meant to say "icc or ifort". I doubt that it is a compiler optimization problem, but that's about all I could think of that would explain this, unless we are assuming something about low-level Unix I/O semantics that isn't true on this platform. Another thing to try would be use of gcc and gfortran instead of icc and ifort, to see if it worked using GNU compilers. If not, then that would eliminate compilers and their run-time support and instead make the file system suspect. The failure is simple enough thst it ought to be possible to come up with a little test case that is independent of netCDF that demonstrates the problem, particularly if it also occurs with non-Intel compilers. --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: BPJ-806970 Department: Support netCDF Priority: Normal Status: Closed