Bug 1562092
| Summary: | du/df hang indefinitely (RHEL Atomic Host 7.4) [rhel-7.4.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Frantisek Sumsal <fsumsal> |
| Severity: | urgent | Docs Contact: | Jaroslav Klech <jklech> |
| Priority: | urgent | ||
| Version: | 7.4 | CC: | ekuric, fkrska, fsumsal, jeder, jklech, jmencak, joedward, jsynacek, mifiedle, msekleta, santony, sbroz, systemd-maint-list |
| Target Milestone: | rc | Keywords: | Reopened, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-219-42.el7_4.11 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, systemd reacted to automount events even when the corresponding unit was masked. Consequently, systemd became unresponsive. This update fixes the bug, and systemd no longer becomes unresponsive under the described circumstances.
|
Story Points: | --- |
| Clone Of: | 1498318 | Environment: | |
| Last Closed: | 2018-04-17 16:37:57 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: | 1498318 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-03-29 13:54:51 UTC
Hi Michal, thank you for the doc text, I have modified it a bit. Could you have a look at it and tell me whether it is correct content-wise? Thank you Jaroslav (In reply to Jaroslav Klech from comment #3) > thank you for the doc text, I have modified it a bit. Could you have a look > at it and tell me whether it is correct content-wise? I guess that doc text gets the message across, but the wording is bit unfortunate. Specifically, use of the word "terminate". systemd as PID1 cannot really terminate (ever) because kernel would panic and reboot the machine immediately. I'd replace it with the word crash. I think we should refrain from using jargon in doc texts (if possible) but trying to use the synonym doesn't really work here and would look silly to people who understand the low-level system details. 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://access.redhat.com/errata/RHBA-2018:1151 |