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.
Hi Evan, The message you are getting: ncdump: roms_avg.0480.nc: File too large looks like a system-level error, rather than an error from ncdump. The string "File too large" doesn't occur anywhere in the netCDF library source code or in the ncdump source code. It is the error message that would be emitted by ncdump in case a system call such as open() returned the system error EFBIG, defined in /usr/include/errno.h. If you run a simple Unix command on the same file, such as wc roms_avg.0480.nc do you get an error, or does it produce the expected output? It would be useful to see a debug trace to find out where the error is coming from, in particular whether from the HDF5 library or the netCDF-4 library. When you run "make check", it runs several large file tests on netCDF-4 that involve files larger than 4 GiB, so what you are seeing is puzzling ... --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: QHK-534643 Department: Support netCDF Priority: Normal Status: Closed