Bug 683551

Summary:	After an unclean reboot systemd does not mount root filesystems rw causing a cascade of launch failures
Product:	[Fedora] Fedora	Reporter:	Alastair Neil <aneil2>
Component:	systemd	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	15	CC:	johannbg, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-09 21:34:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Alastair Neil 2011-03-09 17:09:02 UTC

Description of problem:
root fs not mounted rw 
systemd-tmpfiles-setup.service fails

Version-Release number of selected component (if applicable):
this is f15 alpha

systemd-19-1.fc15.x86_64

How reproducible:

always

Steps to Reproduce:
1. power off system manually
2. reboot

  
Actual results:
many services fail due to readonly / and /tmp

Expected results:
file systems correctly checked and remounted rw


Additional info:

can be worked around by manually remounting the filesystems from a shell.  I even tried running the rescue shell from the DVD and fsck the systems - which pass as clean but I still encounter the issue when I reboot.

Comment 1 Michal Schmidt 2011-03-09 19:46:48 UTC

I am not seeing this problem.
What kind of filesystem do you use?
Please add "systemd.log_level=debug systemd.log_target=kmsg" to your boot parameters, reproduce the problem and get the logs from dmesg.

Comment 2 Alastair Neil 2011-03-09 21:34:32 UTC

Apologies latest yum update resolved the issue.