Open GoogleCodeExporter opened 9 years ago
Do you see the problem with the same zumastor kernel but non-zumastored volume?
Could
you post a sysrq-t trace and server.log if the problem only happens on z
zumastor-ed
volume? Thanks!
Jiaying
Original comment by jiayin...@gmail.com
on 3 Jun 2008 at 1:51
I think the problem is due to the slowness of Zumastor with kernel 2.6.24. I'd
say
what happens is:
1. VMWare starts writing data
2. Data is cached in the cache of the RAID controller (512MB) and maybe in RAM
(I
know this is done for reading but I'm not sure it's done for writing)
3. Data starts to be written to disk but as writes are slow in Zumastor 0.8.0 +
kernel 2.6.24, VMWare deadlocks
I've hit the bug with VMware but I guess other applications would crash as well
if
they do not handle properly very slow writes.
Reproducing the crash is not as easy as I first said. It depends on how much
you need
to write to disk.
The first three times it crashed, it was with 2 virtual machines: Ubuntu Server
and
Windows 2003 Server. As Ubuntu Server installs in only a few minutes and it's a
small
footprint (as opposed to the relatively big footprint of a Windows 2003
installation). The fourth time I tried this, I installed a Windows 2003 fine,
then a
Windows XP, then Ubuntu + Windows 2008 and that was when it crashed.
Original comment by pgqui...@gmail.com
on 4 Jun 2008 at 6:59
Original issue reported on code.google.com by
pgqui...@gmail.com
on 2 Jun 2008 at 3:46