Bug 1076253
Summary: | NFS Root no longer suspends correctly - network is suspended first. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Darryl Bond <darryl.bond> |
Component: | NetworkManager | Assignee: | systemd-maint |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | dcbw, johannbg, lnykryn, msekleta, myroslav, plautrba, slavikvin, systemd-maint, vpavlin, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-06-29 19:27:17 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
Darryl Bond
2014-03-13 22:21:02 UTC
Another yum update and a bit more testing, pm-suspend & systemctl suspend works correctly, systemctl suspend seems to recover better than pm-suspend. but dbus-send --system --print-reply --dest="org.freedesktop.login1" /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true drops the network first and cannot be recovered. I've changed my script to use systemctl suspend instead of dbus-send. Strange how dbus-send... was working fine prior to the update the other day. Found it. NetworkManager was installed but disabled orginally. After the update NetworkManager was re-enabled which must drop the network early in the suspend cycle which then drops access to the filesystems. systemctl disable NetworkManager returned the original good behaviour There is pm-suspend that is "Syncing filesystems" after NetworkManager had already put the network down, while NFS still needs the network to do that fsync operation. On console there were following messages: [ 516.704955] PM: Syncing filesystems ... [ 705.824039] nfs: server srv1 not responding, still trying The almost 190 sec delay is quite consistent between messages. In journal the entries landed with same timestamps for some reason: Nov 03 15:31:58 client1 kernel: PM: Syncing filesystems ... Nov 03 15:31:58 client1 kernel: nfs: server srv1 not responding, still trying It look like syncing in advance (before NetworkManager had put network down) and letting pm-suspend do the sync again later (with nothing to write via network) should save the situation. The only problem is to force NFS start blocking all write requests, before initial sync operation. Any ideas of how to request NFS do that? This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |