h5dump prints output although file doesn't exist.

[hyoklee]

This happens when you define HDF5_DAOS_BYPASS_DUNS=YES.

hyoklee@uan-0002:~> h5dump repack_96_dsets.h5 
HDF5 "repack_96_dsets.h5" {
GROUP "/" {
}
}
hyoklee@uan-0002:~> ls repack_96_dsets.h5 
ls: cannot access 'repack_96_dsets.h5': No such file or directory

[jhendersonHDF]

Are you sure that h5dump isn't printing the contents of a "repack_96_dsets.h5" file that exists in DAOS storage, while regular ls isn't finding the same file outside of DAOS storage?

[hyoklee]

Are you sure that h5dump isn't printing the contents of a "repack_96_dsets.h5" file that exists in DAOS storage, while regular ls isn't finding the same file outside of DAOS storage?

How can I verify it? Is there a way to list file names in DAOS storage other than UUID?

[hyoklee]

Also, I think h5dump should tell user that it's dumping data from DAOS, not from current working directory.

[jhendersonHDF]

How can I verify it?

If you have the HDF5_VOL_CONNECTOR env. var. set, I would probably just unset it first and try again to verify.

Is there a way to list file names in DAOS storage other than UUID?

Not as far as I know, but it's been a little while now since I've worked with the DAOS VOL.

Also, I think h5dump should tell user that it's dumping data from DAOS, not from current working directory.

You could open an issue against HDF5 as an improvement, but it would probably need to be put behind a command-line argument since it would be a change to h5dump's output format.

[hyoklee]

@jhendersonHDF does h5dump

1. call VOL to open file
2. call H5F generic open file if 1. fails?

Is there --trace or --debug option in h5dump so I can see what's being called easily?

[hyoklee]

See also HDFGroup/hdf5#2645