RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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