Description of problem: On boot does not mount NFS mounts from fstab. In my case it is impossible to login as anything but root. How reproducible: Allways Actual results: # systemctl status home.mount home.mount - /home Loaded: loaded (/etc/fstab) Active: inactive (dead) Where: /home What: xx:/home CGroup: name=systemd:/system/home.mount Expected results: # systemctl status home.mount home.mount - /home Loaded: loaded (/etc/fstab) Active: active (mounted) since Tue, 2012-12-25 11:59:19 CET; 19min ago Where: /home What: xx:/home CGroup: name=systemd:/system/home.mount Additional info: An F17 system FedUp'd to F18 beta.
/etc/fstab contains: xx:/home /home nfs defaults 0 0 # mount -va /boot : already mounted /opt : already mounted / : ignored /data : already mounted swap : ignored /dev/shm : already mounted /dev/pts : already mounted /sys : already mounted /proc : already mounted mount.nfs: timeout set for Thu Dec 27 10:54:46 2012 mount.nfs: trying text-based options 'vers=4,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xy' /home : successfully mounted
Please attach a log produced by following these instructions: http://freedesktop.org/wiki/Software/systemd/Debugging#If_You_Can_Get_a_Shell
Created attachment 674297 [details] systemd kernel log
It appears you don't have remote-fs.target enabled for some reason. Try: systemctl enable remote-fs.target
Yes that worked fine! Thanks! The thing is - it worked fine before FedUp'ing to F18.
Hmm, our postinst scripts in systemd actually have enabled remote-fs.target explicitly since about always. Not sure what we can do about this, especially if it's not reproducible.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.