Thanks for the links Ayende, I'll try that today. The firewire driver for win 7 is famous for having problems and the hotfix they released was supposed to fix the corruption problems. It does seems better on my host machine, it is only when using Esent in a guest I have this other issue (only with firewire). I'll keep progress posted here for interests sake.
On Fri, May 21, 2010 at 12:31 AM, Ayende Rahien <[email protected]> wrote: > That is actually a good warning, it means that the VM integration with the > disk is doing some really bad stuff. > At this point, it probably means that you should do something to fix this, > 70 seconds for a local disk write is ridiculous. > > Can you try a HD benchmark tool like: > http://www.simplisoftware.com/Public/index.php?request=HdTach > http://www.iometer.org/ > http://www.passmark.com/products/pt_advdisk.htm > > Try running it on both the host and the guest machines, against the same > HD. > > On Fri, May 21, 2010 at 2:14 AM, Mike Nichols <[email protected]>wrote: > >> This question is really about esent within a virtual environment but >> since it is used in these tools I thot I'd ask here anyways. If you >> aren't running a VM with RSB/RhinoQueues or you don't use firewire >> then I don't want to waste your time :) >> >> I am getting Esent error id 508 when doing integration testing for RSB >> on a VMWare machine. >> This is an I/O error and does not appear when using USB for >> connectivity. >> I already know Win7 firewire drivers are screwed up, but I applied the >> recent hot fix and am not getting the disk errors I was getting >> previously. The vm performs well now, except for this issue. I will >> cross post this to the esent list as well. >> >> Here's my environment: >> >> 1. Guest OS: Win2K3 x86 >> 2. Host OS :Win7 x64 >> 3. Firewire => external hardrive >> >> This error is an I/O error: >> xunit.console (4068) C:\development\materialstesting\build >> \materials_testing.esent86db378e-4e65-475b-82c9-3e54588eba4b: A >> request to write to the file "C:\development\materialstesting\build >> \materials_testing.esent\logs\edb.log" at offset 561152 >> (0x0000000000089000) for 1024 (0x00000400) bytes succeeded, but took >> an abnormally long time (70 seconds) to be serviced by the OS. This >> problem is likely due to faulty hardware. Please contact your hardware >> vendor for further assistance diagnosing the problem. >> >> Any ideas? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Rhino Tools Dev" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<rhino-tools-dev%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/rhino-tools-dev?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rhino-tools-dev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rhino-tools-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
