Bug 840834
Summary: | Endless loop with /.autorelabel | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan Safranek <jsafrane> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | dwalsh, iarlyy, johannbg, jonathan, lnykryn, metherid, msekleta, notting, plautrba, systemd-maint, vpavlin |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-14 19:41:11 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
Jan Safranek
2012-07-17 10:57:58 UTC
Jan is this problem continuing, I have not been able to reproduce it. If you look at the scripts it there something that is blowing up before it gets to the point of removing the autorelabel? It's quite tricky to debug these parts... If I modify /lib/systemd/fedora-autorelabel this way, the system works well, i.e. only one relabel: rm -f /.autorelabel + ( date; ls -la / ) >>/var/log/jsaf + sync systemctl --force reboot Without 'sync', the system enters endless loop of relabelling and I don't see anything in /var/log/jsaf. It seems 'systemctl --force reboot' is not that safe as it claims. I can reproduce it on my virtual machine, rolling rawhide since F14 or so. I had to fix it manually many times, as rawhide breaks up quite often to me. The man page for systemctl claims that "--force reboot" does a umount/remount readonly. This *should* sync the filesystem as well; if it's not, something is going wrong there. I presume this was caused by the issue fixed with "0049f05a8bb82c3e084bacc5945596761d706c55". This has been fixed a while ago in F18. Closing. Please reopen if the issue continues to exist. |