Vivek Goyal c115c4aa45 devmapper: Use transaction mechanism during device or snap device creation ... Finally this patch uses the notion of transaction for device or snapshot device creation. Following is sequence of event. - Open a trasaction and save details in a file. - Create a new device/snapshot device - If a new device id is used, refresh transaction with new device id details. - Create device metadata file - Close transaction. If docker crashes anywhere in between without closing transaction, then upon next start, docker will figure out that there was a pending transaction and it will roll back transaction. That is it will do following. - Delete Device from pool - Delete device metadata file - Remove transaction file to mark no transaction is pending. 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: Use transaction mechanism during device or snap device creation	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