summaryrefslogtreecommitdiffstats
path: root/tools/h5recover/testfiles/test34.h5
diff options
context:
space:
mode:
authorJohn Mainzer <mainzer@hdfgroup.org>2009-04-04 03:58:27 (GMT)
committerJohn Mainzer <mainzer@hdfgroup.org>2009-04-04 03:58:27 (GMT)
commit2bb8a8044afbaa3312dd9dae279b14fab1a6884d (patch)
tree15096c73eabe92d7621411e2a43a5ae920a911d7 /tools/h5recover/testfiles/test34.h5
parent7788ad94856eeefbc06d521f0b7351131cd7a140 (diff)
downloadhdf5-2bb8a8044afbaa3312dd9dae279b14fab1a6884d.zip
hdf5-2bb8a8044afbaa3312dd9dae279b14fab1a6884d.tar.gz
hdf5-2bb8a8044afbaa3312dd9dae279b14fab1a6884d.tar.bz2
[svn-r16670] Interrim checkin of journal file modifications supporting recognition
and rejection of attempts to apply the wrong journal file to a corrupt HDF5 file. Specifically, I made the following changes: 1) Moved all journaling data into the journaling in progress superblock extension message. 2) Added a "magic number" to the journaling in progress message, with the same "magic number being added to the header of the associated journal file. 3) Modifications to library test code to support the above. 4) Modified h5recover to examine the supplied hdf5 file, determine if it is in fact a HDF5 file, if so determine if it is marked as having journaling in progress, and if it does, extract the contents of the journaling in progress super block extension message. 5) Modified h5recover to examine the supplied journal file, determine if it is in fact a HDF5 journal file, and if so, extract the data from its header. 6) Modified h5recover to refuse to apply the supplied journal file to the supplied HDF5 file unless the "magic numbers" obtained from these files matches. 7) Added an examine option to h5recover that causes it to examine and report on the supplied files, but do nothing. This option exists primarily to facilitate testing, but I expect that some users will find it useful as well. 8) Added test code to exercise items 4-7. Note that while I have tried to cover the more likely cases, this test code is extremely cursory. In particular, the code to examine the supplied HDF5 file is barely tested at all. Need a library of HDF5 files exibiting the full range of possible super block and super block extension message structures to test this properly. 9) In passing, tighened up the code that controls dumps of "possibly significant" differences between the contents of the control and recovered data sets in the h5recover. It should now ignore one integer matches in what appears to be garbage raw data. Tested: serial and parallel on Phoenix serial and parallel on Jam serial on Linew serial on Liberty All tests were done in debug mode.
Diffstat (limited to 'tools/h5recover/testfiles/test34.h5')
-rw-r--r--tools/h5recover/testfiles/test34.h5bin0 -> 6752 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/tools/h5recover/testfiles/test34.h5 b/tools/h5recover/testfiles/test34.h5
new file mode 100644
index 0000000..d43b76e
--- /dev/null
+++ b/tools/h5recover/testfiles/test34.h5
Binary files differ