Bug 1298363
| Summary: | docker: Backport device maper deferred device deletion fix in 1.9 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vivek Goyal <vgoyal> |
| Component: | docker | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | lsm5, lsu, vgoyal |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-31 23:23:14 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Vivek Goyal
2016-01-13 22:26:58 UTC
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 |