Page 1 of 1

HDF5 Bug in vhdf5.F

Posted: Fri Nov 22, 2024 8:54 am
by evagol

Hi,

I got the following error while trying to run a job in our cluster:

HDF5-DIAG: Error detected in HDF5 (1.12.2) MPI-process 0:
#000: H5F.c line 532 in H5Fcreate(): unable to create file
major: File accessibility
minor: Unable to open file
#001: H5VLcallback.c line 3282 in H5VL_file_create(): file create failed
major: Virtual Object Layer
minor: Unable to create file
#002: H5VLcallback.c line 3248 in H5VL__file_create(): file create failed
major: Virtual Object Layer
minor: Unable to create file
#003: H5VLnative_file.c line 63 in H5VL__native_file_create(): unable to create file
major: File accessibility
minor: Unable to open file
#004: H5Fint.c line 1898 in H5F_open(): unable to lock the file
major: File accessibility
minor: Unable to lock file
#005: H5FD.c line 1625 in H5FD_lock(): driver lock request failed
major: Virtual File Layer
minor: Unable to lock file
#006: H5FDsec2.c line 1002 in H5FD__sec2_lock(): unable to lock file, errno = 11, error message = 'Resource temporarily unavailable'
major: Virtual File Layer
minor: Unable to lock file
-----------------------------------------------------------------------------
| _ ____ _ _ _____ _ |
| | | | _ \ | | | | / ____| | | |
| | | | |_) | | | | | | | __ | | |
| |_| | _ < | | | | | | |_ | |_| |
| _ | |_) | | |__| | | |__| | _ |
| (_) |____/ \____/ \_____| (_) |
| |
| internal error in: vhdf5.F at line: 85 |
| |
| HDF5 call in vhdf5.F:85 produced error: -1 |
| |
| If you are not a developer, you should not encounter this problem. |
| Please submit a bug report. |
| |
-----------------------------------------------------------------------------

Abort(1) on node 0 (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

--------

I resent the job and everything was ok, but I submit a the report as requested by VASP.

Best,


Re: HDF5 Bug in vhdf5.F

Posted: Fri Nov 22, 2024 9:18 am
by pedro_melo

Dear evagol,

Thank you for the bug report. However, could you provide us with more details about the job in question? Do you still have the same input files, plus the OUTCAR and the standard output and error file produced during the failed run? Also, could you let us know how VASP was compiled and which libraries was it linked to?

All that information is very useful in finding the source of the error.

Kind regards,
Pedro