Most drivers or data formats do not have a built-in integrity mechanism. Thus a successful run of that program does not necessarily mean that the dataset is identical to the state it had just after being generated. The checks performed are generally sufficient to detect whether the dataset is truncated compared to its expected size, but this is not even necessarily guaranteed for some formats (for example the CSV driver may not be able to detect truncation).

Usage: gdal dataset check [OPTIONS] <INPUT>
Check whether there are errors when reading the content of a dataset.
Positional arguments:


  -i, --input <INPUT>                  Input raster, vector or multidimensional raster dataset [required]
Common Options:


  -h, --help                           Display help message and exit


  --json-usage                         Display usage as JSON document and exit


  --config <KEY>=<VALUE>               Configuration option [may be repeated]


  -q, --quiet                          Quiet mode (no progress bar or warning message) [not available in pipelines]
Advanced Options:


  --oo, --open-option <KEY>=<VALUE>    Open options [may be repeated]


  --if, --input-format <INPUT-FORMAT>  Input formats [may be repeated]