Created attachment 950475 [details] lsof output Description of problem: when fsck during boot finds unconsistent root filesystem, and system ends in runlevel 1 single user mode, then is not possible repair FS with its own fsck because FS is busy and cannot be remounted in readonly mode: # LANG=C fsck / fsck from util-linux 2.24.2 e2fsck 1.42.8 (20-Jun-2013) /dev/sda2 is mounted. e2fsck: Cannot continue, aborting. # LANG=C mount -o remount,ro / mount: / is busy lsof shows systemd, systemd-journald, systemd-udev, bash as only running processes, its listing is in attachment. Kernel command line contain "ro", of course, thus root FS should be mounted readonly. Version-Release number of selected component (if applicable): systemd-208-21.fc20.i686 Actual results: Is not possible repair system without booting from some other system - which is not always possible. Moreower, having unconsistent FS mounted RW can result to more serious damage, much more serious than the original. Expected results: 1) FS should be in case its inconsistencies (which cannot be corrected in fsck automaticall repair) mounted readonly. 2) In single user mode should be possible remount all filesystems readonly. These two requirements are possible in systems with sysv init, upstart, openrc.
You can isolate emergency.target. This will give a standalone shell, and it should be possible to remount fs ro.
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.