Vivek Goyal 5be77901cd devmapper: Do not add back device into hash map if meta file removal failed ... When we are deleting a device, we also delete associated metadata file. If that file removal fails, we are adding back the device in in-memory table. I really can't see what's the point. When next lookup takes place it will be automatically loaded if need be. Remove that code. Signed-off-by: Vivek Goyal <vgoyal@redhat.com>		2014-12-03 13:06:43 -05:00
..
aufs	don't call reexec.Init from chrootarchive	2014-11-25 01:03:40 +02:00
btrfs	btrfs: build tag to enable showing version info	2014-11-13 16:43:53 -05:00
devmapper	devmapper: Do not add back device into hash map if meta file removal failed	2014-12-03 13:06:43 -05:00
graphtest	Mknod more loopbacks for devmapper	2014-11-21 16:20:35 -08:00
overlayfs	overlayfs: more helpful output when not supported	2014-11-18 22:53:04 -05:00
vfs	don't call reexec.Init from chrootarchive	2014-11-25 01:03:40 +02:00
driver.go	Merge pull request #7619 from alexlarsson/overlayfs	2014-11-14 22:59:59 +02:00
fsdiff.go	add pkg/chrootarchive and use it on the daemon	2014-11-25 01:03:40 +02:00