delta/docker.git/graphdriver/devmapper, branch release-0.9

devmapper: Increase timeout in waitClose to 10sec

2014-03-18T17:15:44+00:00

As reported in https://github.com/dotcloud/docker/issues/4389 we're
currently seeing timeouts in waitClose on some systems. We already
bumped the timeout in waitRemove() in
https://github.com/dotcloud/docker/issues/4504.

Docker-DCO-1.1-Signed-off-by: Alexander Larsson  (github: alexlarsson)

DeviceMapper: Succeed immediately when removing non-existant devices

2014-03-18T16:57:31+00:00

We've seen situations where removal of "ID-init" failed during
container deletion (EBUSY), after removal of "ID" has succeeded. This
caused the container delete operation to fail, and on the next delete
attempt the removal of "ID" failed immediately with "does not exist".

Ideally we should not fail the ID-init removal, but its also non-ideal
to allow a state where the container is half-removed and we cannot
make progress deleting the container. So, we silently ignore not-exist
errors on device removal.

Docker-DCO-1.1-Signed-off-by: Alexander Larsson  (github: alexlarsson)

devmapper: Increase sleep times and unlock while sleeping

2014-03-18T14:30:53+00:00

We've seen some cases in the wild where waiting for unmount/deactivate
of devmapper devices taking a long time (several seconds). So, we increase
the sleeps to 10 seconds before we timeout. For instance:

https://github.com/dotcloud/docker/issues/4389

But, in order to not keep other processes blocked we unlock the global
dm lock while waiting to allow other devices to continue working.

Docker-DCO-1.1-Signed-off-by: Alexander Larsson  (github: alexlarsson)

devmapper: Add per-device lock

2014-03-18T14:30:28+00:00

We currently use a global lock to protect global data (like the
Devices map) as well as device data itself and access to
(non-threadsafe) libdevmapper.

This commit also adds a per-device lock, which will allow per-device
operations to temporarily release the global lock while e.g. waiting.
The per-device lock will make sure that nothing else accesses that
device while we're operating on it.

Docker-DCO-1.1-Signed-off-by: Alexander Larsson  (github: alexlarsson)

Fix typo in devmapper driver_test

2014-03-07T17:20:25+00:00

Docker-DCO-1.1-Signed-off-by: Paul Morie  (github: pmorie)

Merge pull request #4062 from alexlarsson/clean-shutdown

2014-02-13T18:45:03+00:00

devmapper: Fix shutdown warnings

Merge pull request #4056 from alexlarsson/fix-devmapper-test

2014-02-13T13:06:50+00:00

devicemapper: Fix tests on fedora

Merge pull request #4055 from alexlarsson/remove-devmapper-dirs

2014-02-11T22:05:56+00:00

devmapper: Remove directory when removing devicemapper device

devmapper: Remove byHash hack

2014-02-11T12:02:00+00:00

We no longer pass "pool" anywhere that uses byHash() per the last
commit, so we can now remove this hack.

Docker-DCO-1.1-Signed-off-by: Alexander Larsson  (github: alexlarsson)

devmapper: Fix shutdown warnings

2014-02-11T11:47:59+00:00

Shutdown contains debug warnings like:

[debug] deviceset.go:699 [deviceset docker-0:33-17945897] waitRemove(/dev/mapper/docker-0:33-17945897-pool)
[debug] deviceset.go:380 libdevmapper(3): libdm-common.c:552 (-1) Device /dev/mapper/docker-0:33-17945897-pool not found

This is because shutdown is using removeDeviceAndWait() to remove the pool device and the
wait part fails because the pool is gone.

We fix this by adding a pool specific removal function which avoids all the trickiness of the
normal remove.

Docker-DCO-1.1-Signed-off-by: Alexander Larsson  (github: alexlarsson)