用py3中的h5py打开后，用h5py py2制成的hdf5损坏

Question

Problem

I have a file created with h5py in python 2.7.

These steps lead to a corruption:

1. I download a fresh copy of it from a collaborator using scp . It is whole and 286MB.

2. I check that it is readable by opening it with hdfview . This shows all the datasets and groups properly.

3. I exit hdfview.

4. Repeat steps 2 and 3 to ensure hdfview is not corrupting the file.

5. I open ipython 3.6 and,

   import h5py f = h5py.File(filename,'r') g = f['/sol000']#one group that should be there

I get KeyError: "Unable to open object (Object 'sol000' doesn't exist)"

6. I f.close() and exit ipython. I again open it with hdfview and the entire structure is gone. The file is now 4KB.

I am able to open the file in python 2 hdf5 and access all the datasets, but must use python 3 for my code.

Systems

File created on Fedora 24 64-bit, python 2.7, hdf5 2.7.0

System trying to read it on Fedora 25 64-bit python 3.6, h5py 2.7.0

Minimal code showing should work

On system 1:

import h5py
import numpy as np
f = h5py.File("file.hdf5","w")
f.create_dataset("/sol000/data",(100,100),dtype=float)
f["/sol000/data"] = np.zeros([100,100],dtype=float)
f.close()

On system 2: Do steps 1-4.

import h5py
f = h5py.File("file.hdf5","r")
f.visit(lambda *x:print(x))
#(sol000/data,)
f.close()

Answer 1

The solution was to enforce libver=earliest . Ie the following code worked to open the file:

import h5py
f = f.File("file.hdf5","r",libver="earliest")

I've discovered a possible inconsistency in h5py documentation. It claims that

The “earliest” option means that HDF5 will make a best effort to be backwards compatible.

The default is “earliest”.

This can't be true if it only works when I explicitly set it. My collaborator, it turns out, created the corruptable file with an older version of hdf5 C library.