summaryrefslogtreecommitdiff
path: root/pkg/devicemapper/devmapper_wrapper.go
Commit message (Collapse)AuthorAgeFilesLines
* loopback: separate loop logic from devicemapperVincent Batts2015-12-181-41/+0
| | | | | | | | The loopback logic is not technically exclusive to the devicemapper driver. This reorganizes the code such that the loopback code is usable outside of the devicemapper package and driver. Signed-off-by: Vincent Batts <vbatts@redhat.com>
* devicemapper: remove unused type mappingVincent Batts2015-12-181-2/+1
| | | | Signed-off-by: Vincent Batts <vbatts@redhat.com>
* Remove (?) from comments in pkg/devicemapperVincent Demeester2015-09-301-2/+2
| | | | | | Got merged with it, removing it as it doesn't add anything. Signed-off-by: Vincent Demeester <vincent@sbr.pm>
* Lint package pkg/devicemapperVincent Demeester2015-09-051-32/+35
| | | | Signed-off-by: Vincent Demeester <vincent@sbr.pm>
* devicemapper: fix zero-sized field accessVincent Batts2015-08-101-3/+15
| | | | | | | | | | | | Fixes: #15279 Due to https://github.com/golang/go/commit/7904946eeb35faece61bbf6f5b3cc8be2f519c17 the devices field is dropped. This solution works on go1.4 and go1.5 Signed-off-by: Vincent Batts <vbatts@redhat.com>
* devicemapper: Create a method to get device info with deferred remove fieldVivek Goyal2015-04-211-23/+24
| | | | | | | | | | Deferred reove functionality was added to library later. So in old version of library it did not report deferred_remove field. Create a new function which also gets deferred_remove field and it will be called only on newer version of library. Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
* devicemapper: Add helper functions to allow deferred device removalVivek Goyal2015-04-211-0/+1
| | | | | | | | | | | | A lot of time device mapper devices leak across mount namespace which docker does not know about and when docker tries to deactivate/delete device, operation fails as device is open in some mount namespace. Create a mechanism where one can defer the device deactivation/deletion so that docker operation does not fail and device automatically goes away when last reference to it is dropped. Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
* Fix vet warning in devicemapper.Félix Baylac-Jacqué2015-03-271-3/+3
| | | | | | Issue #11828 Signed-off-by: Félix Baylac-Jacqué <baylac.felix@gmail.com>
* Merge pull request #10197 from vbatts/vbatts-dm_cookie_supportMichael Crosby2015-01-271-0/+5
|\ | | | | devicemapper: API for cookie support
| * devicemapper: API for checking cookie supportVincent Batts2015-01-191-0/+5
| | | | | | | | Signed-off-by: Vincent Batts <vbatts@redhat.com>
* | devicemapper: define the fallback flagVincent Batts2015-01-191-0/+1
|/ | | | | | | | | | | DM_UDEV_DISABLE_LIBRARY_FALLBACK is disabled by most applications today when using device-mapper, and ensuring that device-mapper is in sync with udev. This flag instructs devicemapper to not fallback to creating the device nodes itself. In the case of udev sync not being supported, devicemapper will attempt to create the devices in a timely manner, regardless of udev. Signed-off-by: Vincent Batts <vbatts@redhat.com>
* devicemapper: dm_udev_get_sync_supportVincent Batts2015-01-191-0/+10
| | | | | | expose an api to call dm_udev_get_sync_support/dm_udev_set_sync_support Signed-off-by: Vincent Batts <vbatts@redhat.com>
* devmapper: use proper DM_UDEV_DISABLE_*_FLAG when creating the thin-poolMike Snitzer2014-11-121-0/+6
| | | | | | | | Otherwise udev can unecessarily execute various rules (and issue scanning IO, etc) against the thin-pool -- which can never be a top-level device. Docker-DCO-1.1-Signed-off-by: Mike Snitzer <snitzer@redhat.com> (github: snitm)
* devicemapper: split out devicemapper bindingsVincent Batts2014-11-051-0/+254
This is a first pass at splitting out devicemapper into separate, usable bindings. Signed-off-by: Vincent Batts <vbatts@redhat.com>
View Lorry Controller Status