I just switched from Fedora 18 to Fedora 20 and figured out that the system can not be remounted ro by issuing mount / -o ro,remount This usually returns "/ busy" as answer. After some investigations I figured out that "alsa-state.service" is the cause of keeping the system busy. This was NOT the case in any older Fedora versions < 18 and took me a long time to figure out. I would like to ask whether alsa-state.service can be reviewed to NOT keep / busy and immidiately allow a remount read-only as it used to be in pre systemd times and all other systems ?
most likely because of alsactl daemon or alsactl rdaemon
Please, attach output from 'lsof -p <pid>' where <pid> is the alsactl task in time where the busy error is returned from mount...
Hello! Sorry for the late response! After some more investigations I figured out that not alsa is causing the problems but journald. https://bugzilla.redhat.com/show_bug.cgi?id=1046313 It looks that whenever journald is being "stopped" it instantly respawns as soon as some new stuff is being sent to be logged. Initially I went from one service to another service to be shut down only to figure out what caused the system from preventing to get re-mounted in read-only and to my surprise whenever I (also) killed alsa-state the system reacted as expected and let me remount in read-only. From what I understand now this is not alsa-state related but rather a "problem" of journald's implementation.
Thanks, closing as a duplicate. *** This bug has been marked as a duplicate of bug 1046313 ***