# Accessing Fletcher32 checksum **URL:** \ **Category:** HDF5 Library\ **Created:** [July 17, 2020, 1:14pm UTC](https://forum.hdfgroup.org/t/accessing-fletcher32-checksum/7299 "2020-07-17T13:14:23Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ken.walker](https://forum.hdfgroup.org/letter_avatar_proxy/v4/letter/k/b38774/32.png) [@ken.walker](https://forum.hdfgroup.org/u/ken.walker)\ **Post date:** [July 17, 2020, 1:56pm UTC](https://forum.hdfgroup.org/t/accessing-fletcher32-checksum/7299/2 "2020-07-17T13:56:28Z")
Did you see this post from 2018? It doesn’t answer your question, but explains error checking behavior. I have the impression you can’t get the checksum value. **Data corruption detection and/or correction** > [@Data corruption detection and/or correction](https://forum.hdfgroup.org/t/data-corruption-detection-and-or-correction/4361): > > So, HDF5 lib has ability to do checksuming on any data passing from client to file via H5Dwrite/H5Dread, correct? This can be used to detect data corruption. Just curious, but has there ever been any discussion of extending this functionality to attribute data, HDF5 lib metadata, etc? The way current checksuming is intended to work now is that data is checksumed on write and the checksum is stored for each chunk of a dataset. And, only upon read is detection of possible data corruption actually… --- _[View the full topic](https://forum.hdfgroup.org/t/accessing-fletcher32-checksum/7299)._