For some context see:
https://github.com/docker/docker/pull/12354#issuecomment-121958324
and
@SamSaffron
I think we have made lot of progress on improving devicemapper graph driver. Lot of issues are because of static binary and I think many of the issues are configuration issues. Based on configuraiton, one can easily switch between loop based thin pool, or thin pool on block devices or
usage of external lvm thin pool. If such switch happens, data in /var/lib/docker/devmapper/ is stale
and all sorts of errors will happen.
To make things little better and detect configuation issues early, I have created following PR. This should help a bit I think.
#13896
For our most recent corruption, I don’t know if the docker binary was statically or dynamically compiled, I do know it was using latest docker.
We have been burnt so many times by device mapper that my confidence is totally eroded.