Hey guys. I just wanted to see if anyone else is having a problem with the NotFred VM. After a while, I get an error about writes outside the hda1 area. I did some invesigation and might have found a reason. After checking out the web interface, I found that the WU that was completed and from what I can tell was sent is still in the 'instance' directory. The whole directory has grown to 126MB. I'm not sure where the other room has gone, but the Virtual disk is now at its full size. I'm not sure how to find out where the other space is at. I know how to use ls -al and df in linux, but is there any other command to try?
To 'NotFred' could you check this out? I'm running VMServer 1.06 with your latest folding VM files (which rock with the a2 core btw). It seems after one or 2 completed cores, the virtual disk fills up so maybe if you could do a scheduled job to check for sent WUs (and I have no clue how to know if they are sent) and remove them after the next WU starts. Maybe this will allow linux to release them to be deleted. I love the VM and would love for it to become as reliable as possible. I'm guessing that maybe the timer not syncing with the host might be causing the built in stanford process to no longer work. Anyway, if anyone else can duplicate this, I would appreciate it. I guess the only other request if a cleanup script isn't possible, that maybe we can get a larger max size on the virtual disk. 512MB is just a wee bit tiny with these large WUs.