-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creation of a utility to help recover raw data files that were not cleanly closed #106
Conversation
…ally write the Attributes that might be needed to recover a file.
I've tested and the tests work as stated, so I think those look good. I'll approve given that. One thing that came up though: I saw errors like this (that were caught appropriately I think):
Is this expected for files needing recovery? If so, maybe this is a separate issue to try to better recover these attributes (if we think we need to)? Where 'try to recover' may be writing these at file open or something like that? |
…ta types for creation_timestamp and closing_timestamp Attributes
Yes, I haven't looked very closely at the errors that we see from the last TriggerRecord in the un-closed PDS files, but now that you mention the details of those errors, it does seem like they may be recoverable. I ran |
Usage:
HDF5LIBS_TestRecoverFile [-R] <filename>
This app has two modes.
The first mode (without the "-R" command-line option), prints out information about the relevant HDF5 file-level Attributes in the file. It also prints out the values that will be used if/when the file is recovered.
The second mode (with the "-R" command-line option), sets necessary HDF5 Attributes in the file to appropriate values.
Re-running this app on a recovered file is possible, and this can be useful in verifying that the changes that were made were reasonable.
There are a couple of broken files in
np04-srv-005:/data2/kurtMetadataTests/reference/
that can be used for testing this new app. If you use "cp -p