moby/daemon/graphdriver
Vivek Goyal 17b75a21a6 devmapper: Use transactions during device deletion
Use transaction logic during device deletion and do rollback if transaction
is not complete. Following is the sequence of events.

- Open transaction and save to metafile
- Delete device from pool
- Delete device metadata file from disk
- Close Transaction

If docker crashes without closing transaction then rollback will take
place upon next docker start.
 
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 transactions during device deletion 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