It looks like it locks up when used as root (afr/replicate) at the point
where it initially starts up udev (not 100% sure where exactly yet, will
have to put some trace code in rc.sysinit).
2.0.0rc2 didn't have this problem.
Unfortunately, I don't think I can provide any log output due to it
being the rootfs (the only way I can think of for logging in that
use-case is syslog support).
The file system not being accessible immediately after mounting also
appears to still be the case with rc4, as it has been with previous
versions. While it is possible to doctor mount.glusterfs to put a sleep
and "ls -la > /dev/null" into it to work around the problem, it's a bit
naf - glusterfs shouldn't really return until everything is ready for
immediate access.
Gordan