Vivek Goyal 4d39e056aa devmapper: Keep track of used device Ids in a bitmap ... Currently devicemapper backend does not keep track of used device Ids in the pool. It tries a device Id and if that device Id exists in pool, it tries with a different Id and keeps on doing this in a loop till it succeeds. This worked fine so far but now we are moving to transaction based device creation and deletion. We will keep deviceId information in transaction which will be rolled back if docker crashed before transaction was complete. If we store a deviceId in transaction and later figure out it already existed in pool and docker crashed, then we will rollback and remove that existing device Id from pool (which we should not have). That means, we should know free device Id in pool in advance before we put that device Id in transaction. Hence this patch creates a bitmap (one bit each for a deviceId), and sets the bit if device Id is used otherwise resets it. This patch is just preparing the ground right now. Actual usage will follow in later patches. 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: Keep track of used device Ids in a bitmap	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