Bug 642903

Can you attach the .wsf file?  You have to start from "Browse Infrastructure Logs" in the DTM Studio.

(In reply to comment #1)
> Can you attach the .wsf file?  You have to start from "Browse Infrastructure
> Logs" in the DTM Studio.

Hi Paolo,
  When tun Disk Verification job in win2008-64 guest, the result is failed too.

  I start from "Browse Infrastructure Logs" in the DTM Studio, there is no .wsf file, so I attach WttEa.log (win2008-64) file which in same folder.

Thanks!

Created attachment 453610 [details]
win2008-64-WttEa.log

It's \\S1-rhev-m.S1domain.com\DTMLogs\\9958CF65-C41D-4483-8081-4D5A8ED064BD\E6724836-DAB2-46B2-80F3-19C8F039FFE6\5D3C2DDE-C5D1-4C87-80C9-7522D243167E\diskIO.wtl or any diskIO.wtl log you find from "Browse Infrastructure Logs" (I confused the two extensions).

(In reply to comment #4)
> It's
> \\S1-rhev-m.S1domain.com\DTMLogs\\9958CF65-C41D-4483-8081-4D5A8ED064BD\E6724836-DAB2-46B2-80F3-19C8F039FFE6\5D3C2DDE-C5D1-4C87-80C9-7522D243167E\diskIO.wtl
> or any diskIO.wtl log you find from "Browse Infrastructure Logs" (I confused
> the two extensions).

Hi Paolo, 
It is \\S1-rhev-m.S1domain.com\DTMLogs\\9958CF65-C41D-4483-8081-4D5A8ED064BD\E6724836-DAB2-46B2-80F3-19C8F039FFE6\5D3C2DDE-C5D1-4C87-80C9-7522D243167E\diskIO.wtl.
Thanks.

Created attachment 453982 [details]
diskIO.wtl

FWIW, the full 3-day test passed for me on W2K8R2.

It shouldn't matter because the job only touches the single disk that you specify in the device console---anyway, yes, I'm using 3 for everything except boot test and now crashdump too.

It shouldn't matter because the job only touches the single disk that you specify in the device console---anyway, yes, I'm using 3 for everything except boot test and now crashdump too.

It shouldn't matter because the job only touches the single disk that you specify on the command line---anyway, yes, I'm using 3 for everything except boot test and now crashdump too.

(In reply to comment #12)
> It shouldn't matter because the job only touches the single disk that you
> specify on the command line---anyway, yes, I'm using 3 for everything except
> boot test and now crashdump too.

According to our latest test result:
when set it as '3', I'll get BSOD in a short time.
when set it as '1', the job will run 3 days but fails at last.

Any idea?

Can I get the BSOD screenshot and memory dump?

Created attachment 459331 [details]
screen shot of BSOD when set EnumateDevice=3

You can get MEMORY.DMP from ftp://10.66.93.232/tmp/ (I cannot access file.nay.redhat.com with my today)

This job also fails with xenpv-win-1.3.1.el5 when setting 'EnumerateDevices=3' and 'EnumerateDevicesOverride=3'

I have placed additional Xen packages for this bug (actually for bug 651912) at http://people.redhat.com/pbonzini/disk-verification

The packages are supposed to run with EnumerateDevicesOverride=3 (EnumerateDevices doesn't matter).

New error:

Error in testcase "Random verify on File F:\testfile.bin's clusters". Exception 
  Message Adding the given count to the semaphore would cause it to exceed its maximum count. 
  TargetSite Int32 Release(Int32) 
  StackTrace 
   StackFrame 
    Class System.Threading.Semaphore 
    Method Release 
    Signature Int32 Release(Int32) 
   StackFrame 
    Class DiskIO.DiskIOTestCase 
    Method RunScenario 
    Signature Void RunScenario(Microsoft.Win32.SafeHandles.SafeFileHandle, System.String) 
   StackFrame 
    Class DiskIO.DiskIOTestCase 
    Method Run 
    Signature Void Run() 
  Source System 
  HResult 0x80131501

Latest state: still BSODs on W2k8-32, fails with errors of comment #7 and comment #18 on other systems.

Still waiting to analyze the BSOD to understand whether it is attributed to the drivers or to bug 651912.

Update from cshao: with the fixes for bug 651912,

> We test Disk Verification job with single disk, set DWORD value 
> "EnumerateDevicesOverride" =3; "EnumerateDevices"=1
> It can pass in win2008R2 guest.
> 
> But win2008-32/64 are still fail. Fail reason is "Random verify on File
> C:\testfile.bin".

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.

Pass with xenpv-win-1.3.1-1.el5.noarch.rpm when data disk's driver is tap:aio, device is Virtual Disk(xvda) and EnumerateDevicesOveride=3.