I don't want to bother you with my partition problems (or my bad english :-). I've just the question if it is possible that mprime can cause a damaged partition, because mprime actually don't need any disc space for the computations. Could it be a problem of Vmware ESX because it is optimized for server consolidation and not for computations in this extent?
we had a discussion of just about this a short while ago on this list.
the only scenario I could see where this might happen would involve an overheating processor misexecuting a disk related calculation, or corrupting a directory entry buffer in memory, and then using this miscalculation to write back to the disk, stepping on the superblock or MFT or root directory or FAT (or whatever equivalent is in your systems file system).
I've run two instances of mprime on a pair of dual xeon servers with Linux for well over a year now without any mishaps. True, I wasn't running VMware, but I can't see how that would matter.
_______________________________________________
Prime mailing list
[email protected]
http://hogranch.com/mailman/listinfo/prime
