Vivek Goyal b210423311 devicemapper: Check loop devices of existing pool ... Often it happens that docker is not able to shutdown/remove the thin pool it created because some device has leaked into some mount name space. That means device is in use and that means pool can't be removed. Docker will leave pool as it is and exit. Later when user starts the docker, it finds pool is already there and docker uses it. But docker does not know it is same pool which is using the loop devices. Now docker thinks loop devices are not being used. That means it does not display the data correctly in "docker info", giving user wrong information. This patch tries to detect if loop devices as created by docker are being used for pool and fills in the right details in "docker info". Signed-off-by: Vivek Goyal <vgoyal@redhat.com>		2015-07-07 14:13:29 -04:00
..
attach_loopback.go	Replace aliased imports of logrus, fixes #11762	2015-03-26 23:22:04 +01:00
devmapper.go	devicemapper: Check loop devices of existing pool	2015-07-07 14:13:29 -04:00
devmapper_log.go	devicemapper: Create helpers to cancel deferred deactivation	2015-04-21 18:14:59 -04:00
devmapper_wrapper.go	devicemapper: Create a method to get device info with deferred remove field	2015-04-21 18:14:59 -04:00
devmapper_wrapper_deferred_remove.go	devicemapper: Create a method to get device info with deferred remove field	2015-04-21 18:14:59 -04:00
devmapper_wrapper_no_deferred_remove.go	devicemapper: Create a method to get device info with deferred remove field	2015-04-21 18:14:59 -04:00
ioctl.go	devicemapper: split out devicemapper bindings	2014-11-05 18:10:38 -05:00
log.go	devicemapper: define device-mapper log levels	2015-01-20 13:31:12 -05:00