[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #OYM-954504]: netcdf/lustre bug

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.

  • Subject: [netCDF #OYM-954504]: netcdf/lustre bug
  • Date: Tue, 06 Jun 2017 20:38:34 -0600
For all normal file systems, a file IO operation that fails
is not retryable. So you cannot be surprised that we do not retry.
However, if we get an error and do not report it, that is indeed an error
on our part. You say we zero and continue. You can save me some time
if you indicate the file and line in which this occurs. I would appreciate it.
Also, if there is some way we can tell at run time that we are using lustre,
we can add a hack to do the retry. Do you know if such a test is possible
and what the code would look like?
=Dennis Heimbigner
  Unidata


Ticket Details
===================
Ticket ID: OYM-954504
Department: Support netCDF
Priority: Normal
Status: Open
===================
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.