Bug 642903 - The Disk Verification (LOGO) failed in win2008R2 and win2003 BLK
Summary: The Disk Verification (LOGO) failed in win2008R2 and win2003 BLK
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xenpv-win
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Paolo Bonzini
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 651912
Blocks: 518435
TreeView+ depends on / blocked
 
Reported: 2010-10-14 05:24 UTC by cshao
Modified: 2011-01-27 09:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 651912 (view as bug list)
Environment:
Last Closed: 2011-01-27 09:15:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
win2008-64-WttEa.log (2.76 MB, text/plain)
2010-10-15 01:38 UTC, cshao
no flags Details
diskIO.wtl (730.92 KB, text/plain)
2010-10-18 01:48 UTC, cshao
no flags Details
screen shot of BSOD when set EnumateDevice=3 (36.14 KB, image/png)
2010-11-10 06:55 UTC, Rita Wu
no flags Details

Description cshao 2010-10-14 05:24:00 UTC
Description of problem:
The Disk Verification (LOGO) failed in win2008R2 and win2003

Version-Release number of selected component (if applicable):
xenpv-win-1.2.0-1.el5

How reproducible:
always

Steps to Reproduce:
1.Configure WHQL and do BLK win2008R2 or win2003 Disk Verification testing.
2.Disk Verification-this test will last 3x24hours.
3.The Disk Verification (LOGO) failed.
  
Actual results:
The Disk Verification (LOGO) failed.

Expected results:
The Disk Verification (LOGO) pass.

Additional info:
 Below is logo:
------------------------------------------------------------------------------
    TaskResult Errors
    The Execute Task with Commandline "cmd /c diskio.exe /d 'PCI\VEN_5853&DEV_0001&SUBSYS_00015853&REV_01\3&267A616A&0&18' /b 32KB /t 3.00:00:00 /c xv /a " Failed with ExitCode     e0434f4d.

    Resolution
    The task exited with an ExitCode other than the ExpectedTaskExitCode, This may cause the Task to Fail if it is set to Fail On Exit Code.
------------------------------------------------------------------------------

Comment 1 Paolo Bonzini 2010-10-14 12:21:03 UTC
Can you attach the .wsf file?  You have to start from "Browse Infrastructure Logs" in the DTM Studio.

Comment 2 cshao 2010-10-15 01:37:42 UTC
(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!

Comment 3 cshao 2010-10-15 01:38:49 UTC
Created attachment 453610 [details]
win2008-64-WttEa.log

Comment 4 Paolo Bonzini 2010-10-15 12:25:01 UTC
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).

Comment 5 cshao 2010-10-18 01:47:30 UTC
(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.

Comment 6 cshao 2010-10-18 01:48:23 UTC
Created attachment 453982 [details]
diskIO.wtl

Comment 8 Paolo Bonzini 2010-11-08 13:23:09 UTC
FWIW, the full 3-day test passed for me on W2K8R2.

Comment 10 Paolo Bonzini 2010-11-09 09:43:03 UTC
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.

Comment 11 Paolo Bonzini 2010-11-09 09:43:03 UTC
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.

Comment 12 Paolo Bonzini 2010-11-09 09:43:03 UTC
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.

Comment 13 Rita Wu 2010-11-09 10:46:17 UTC
(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?

Comment 14 Paolo Bonzini 2010-11-09 19:37:58 UTC
Can I get the BSOD screenshot and memory dump?

Comment 15 Rita Wu 2010-11-10 06:55:44 UTC
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)

Comment 16 Rita Wu 2010-11-24 04:50:33 UTC
This job also fails with xenpv-win-1.3.1.el5 when setting 'EnumerateDevices=3' and 'EnumerateDevicesOverride=3'

Comment 17 Paolo Bonzini 2010-11-25 23:35:10 UTC
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).

Comment 18 Paolo Bonzini 2010-11-30 08:18:03 UTC
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

Comment 19 Paolo Bonzini 2010-11-30 08:32:05 UTC
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.

Comment 20 Paolo Bonzini 2010-12-21 12:55:55 UTC
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".

Comment 22 RHEL Program Management 2011-01-11 20:13:47 UTC
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.

Comment 23 RHEL Program Management 2011-01-12 15:23:44 UTC
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.

Comment 24 Rita Wu 2011-01-27 09:15:33 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.