[uml-user] COW file on ubd4 lockup (continued)

[Nathan M. <nmi...@vi...>]

It looks like actually the following process cooked my ubd0 
partitions.  even removing the ubd4 section from my startup causes the same 
errors now.  So I just mounted them as loopback devices on the host and get 
crud like this:

Mounted to /mnt

# cd /mnt/var/run
# ls
ls: sudo: Permission denied
ls: console: Permission denied
ls: radvd: Permission denied
ls: netreport: Permission denied

Most other directories do ls's just fine.  Any clue what I did to cause this?

--- copy of previous post ---

Trying to share a filesystem between two uml systems.  I am trying to mount 
a 10G partition between 2 different umls on ubd4.  My command line looks 
like this:

linux con=pty con0=fd:1,fd:2 ubd4=shared_cow,shared_fs mem=64M

Trying to boot onto a redhat-7.2 partion on ubd0 it gets past the kernel 
boot and then starts spewing errors.

rm: cannot remove /var/lock/subsys: Permission denied
rm: cannot remove /var/run/console: Permission denied
rm: cannot remove /var/run/netreport: Permission denied
rm: cannot remove /var/run/radvd: Permission denied
rm: cannot remove /var/run/sudo: Permission denied
/etc/rc.sysinit: /var/run/utmp: Input/output error
etc..
etc...

then when it gets to "Starting system logger:" the uml machine locks up and 
I have to kill it off.

I know all the examples talk about cow files for ubd0, but shouldn't it 
work as well for ubd4?

I've confirmed the creation of the cow file.  I do not know if it finished, 
but it created a 34M cow file for my 10GB shared filesystem I'm trying to 
mount.