Vivek Goyal b721d6d8d0 devmapper: Do not check for transaction id during device metadata loading ... Again, just because device transaction id is greater than pool transaction id, it does not guarantee that device is in the pool. So do not check of this during loading of device metadata. Docker needs to deal with it. And device activation will fail when we try to activate a device for whom metafile is present but there is no device in the pool. 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 check for transaction id during device metadata loading	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