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.
Joerg, > I wrote: > > In the meantime, understanding and finding a fix for this problem will > > be a priority, even though it has apparently been a bug in the library > > for years, at least since the release of netCDF-3.6.2. I also > > intend to determine when the bug first appeared in a netCDF release, > > as that may help in fixing the problem. > > Version 3.5.1 from Feb. 17, 2004 appears to be free of the bug, but it's in > the > next release, version 3.6.0, from Dec. 18, 2004. We were using cvs back then > rather than svn for version control, but I may be able to access the history > of > checkins and narrow down which checkin first introduced the bug ... Actually, as a result of more careful testing, that's wrong. Version 3.5.1 had the bug, and as far as I can tell now, no version of netCDF has ever handled large block sizes, such as Lustre uses, correctly. It looks like there's no shortcut to fixing this, it will require understanding the optimized buffering code ... --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: RPZ-106941 Department: Support netCDF Priority: Critical Status: Closed