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
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.