Red Hat Bugzilla – Bug 213132
first boot into a filesytem with TEMPORARY_STATE=y fails in spectacular ways
Last modified: 2014-03-16 23:03:38 EDT
Description of problem:
When setting TEMPORARY_STATE=y in /etc/sysconfig/readonly-root with READONLY=no
on first boot you get some failures to mount various parts of the filesystem.
Version-Release number of selected component (if applicable):
Only on first boot with a fresh filesystem.
Steps to Reproduce:
1. Download an OLPC image
2. Burn that image to a USB key or drive
3. Mount the drive and change the readonly-root config file to add the y
4. Boot in qemu and enjoy!
You get error messages such as:
Setting hostname localhost.localdomain [ OK ]
raidautorun: failed to open /dev/md0: No such device or address
can't create lock file /etc/mtab~1244: Read-only file system (use -n flag to
mkdir: cannot create directory '/var/lib/stateless/writable/var': Read-only
mount: special device /var/lib/stateless/writable/var/lock does not exist
No errors! It must be perfect!
Some possible things that might be going on:
1. Very often the filesystem might be mounted as read only the first time around
due to it being dirty
2. I suspect that this might be a missing -n on a mount somewhere - probably
when first mounting /var/lib/stateless/writable?
Fixed in CVS.
initscripts-8.45.4-1 has been pushed for fc6, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
initscripts-8.45.5-1 has been pushed for fc6, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.