Red Hat Bugzilla – Bug 991207
Service fedora-readonly hang indefinitely
Last modified: 2014-03-16 23:34:00 EDT
Description of problem:
When using a read-only nfs share as the root filesystem, the fedora-readonly service stalls forever at "A start job is running for Configure read-only root support".
I was able to resolve the problem to my satisfaction by commenting some lines that were not present in Fedora 18, but I want to let you know about the change in behavior after Fedora 18.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Prepare a Fedora setup to be used as a stateless read-only root filesystem and export it with nfs:
A: Modify the variables in /etc/sysconfig/readonly-root:
B: Remove all lines in /etc/fstab
2. Prepare an init ram filesystem for network boot with these commands:
yum -y install dracut-network
dracut -N initrd-fc19.img `uname -r`
3. Make the kernel and the new init ram filesystem available to the diskless client and have it boot the Fedora kernel with theses arguments (we use pxelinux):
The start sequence stalls at the following message:
"A start job is running for Configure read-only root support"
In Fedora 17 and Fedora 18, this method would provide a Fedora startup that worked exactly as it did on the originally installed computer.
I was able to make it work again in Fedora 19 by commenting these lines in
# if mount | grep -q /var/lib/nfs/rpc_pipefs ; then
# mount -t rpc_pipefs sunrpc /var/lib/nfs/rpc_pipefs && service rpcidmapd restart
So, I guess the problem might be with the restart of the rpcidmapd service.
Hi, this is fixed in version 9.48-1, so closing as RAWHIDE.