On 05/01/2018 16:39, Jordan Henderson wrote:
Thanks for the detailed explanations, Jordan. All understood and
appreciated.
For your last question, this is likely a side effect of an elusive bug
that has also existed in HDFView for a while now. The root cause hasn't
yet been discovered but it has been noticed that occasionally simply
opening a file and closing it at a later time seems to show that some
modification has been made to the HDF file. I imagine that the change it
is making to the file is something metadata-related which would explain
why killing the process corrupts the file. Could you possibly rerun h5ls
on the corrupted file with the additional "--enable-error-stack"
command-line parameter so that we can at least capture and keep a record
of the specific error that HDF5 is running into when it tries to open
the file? This may be very helpful in debugging the root problem.
This isn't showing any extra detail I'm afraid:
% h5ls -r --enable-error-stack idr016-orig.h5
/ Group
/Images Dataset {69120/Inf}
/Objects Dataset {5880380/Inf}
% h5ls -r --enable-error-stack idr016-broken.h5
idr016-broken.h5: unable to open file
% h5ls --enable-error-stack idr016-broken.h5
idr016-broken.h5: unable to open file
Kind regards,
Roger
The University of Dundee is a registered Scottish Charity, No: SC015096
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5
