Bug 1314693
| Summary: | Fix rule setting SYSTEMD_READY=0 for DM devices (like multipath) which may cause improper automatic unmounts | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Libor Miksik <lmiksik> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Radka Brychtova <rskvaril> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.3 | CC: | bblaskov, fkrska, matt.schulte, mnavrati, ng-hsg-engcustomer-iop-bz, prajnoha, rsawhill, rskvaril, Ryan.Rodine, systemd-maint-list, systemd-maint, yhuang |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-219-19.el7_2.7 | Doc Type: | Bug Fix |
| Doc Text: |
The device mapper sets the DM_UDEV_DISABLE_OTHER_RULES_FLAG signal to indicate that other rules should not react to the event. However, systemd previously considered the related device not to be ready for use, which is only true for the ADD event. As a consequence, overlaying file systems on the devices were unmounted even if only one path became unavailable, but other paths were still accessible. With this update, the device is marked as unusable only in case of ADD events, and CHANGE events are ignored. As a result, file systems are no longer unmounted if a CHANGE event occurs.
|
Story Points: | --- |
| Clone Of: | 1312011 | Environment: | |
| Last Closed: | 2016-03-31 21:55:48 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1312011 | ||
| Bug Blocks: | |||
|
Description
Libor Miksik
2016-03-04 09:19:01 UTC
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-0181.html |