Hide Forgot
Description of problem: Device mapper graphdriver deferred device deletion feature has a bug which I recently fixed upstream and will show up in 1.10. As we will be enabling deferred device deletion by default in 1.9, I think it is important to backport that fix in 1.9. https://github.com/docker/docker/pull/19241 Version-Release number of selected component (if applicable): 1.9.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Could you open a pull request on the rhel7-1.9 branch.
Ok, will do
Did this ever happen, or not fixed until docker-1.10
I think it got pulled into rhel 1.9. https://github.com/projectatomic/docker/pull/65
Fixed in docker-1.9
I can only verify this by watching the log and the patch witin docker-1.9.1-23.el7.x86_64, Starting docker daemon with #docker daemon --storage-opt dm.use_deferred_removal=true --selinux-enabled --storage-opt dm.use_deferred_deletion=true -D Trigger defer remove: #docker run -ti --rm rhel7 /bin/bash #docker run -ti -v /:/host rhel7 bash exit the first container will trigger: Deferred Deleted Device Count: 1 and after exit the second later, it will be to zero later
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0536.html