BUG: Deadlock on Table with Text/Image Column May Cause ErrorsLast reviewed: June 18, 1997Article ID: Q170296 |
The information in this article applies to:
SYMPTOMSHeavy stress that causes an extremely high number of deadlocks on a table with image/text columns may cause the following errors and cause the server to stop responding:
udread: Operating system error 38(Reached end of file.) on device 'C:\MSSQL\DATA\MASTER.DAT' (virtpage 0x00ffff00). Buffer 10da140 from database 'MSS' has page number 2855763 in the page header and page number -256 in the buffer header mirrorproc: i/o error on primary device 'C:\MSSQL\DATA\MASTER.DAT' udread: Operating system error 6(The handle is invalid.) on device 'C:\MSSQL\DATA\MASTER.DAT' (virtpage 0x00000114). udread: Operating system error 6(The handle is invalid.) on device 'C:\MSSQL\DATA\MASTER.DAT' (virtpage 0x00000394). udread: Operating system error 6(The handle is invalid.) on device 'C:\MSSQL\DATA\MASTER.DAT' (virtpage 0x00000105). bufwait: timeout, BUF_IO, bp 0x10fdea0, pg 0x110, stat 0x1004/0x6, obj 0x1d906ebe, bpss 0The errorlog is filled with bufwait error messages until server is killed (it cannot shut down normally); all existing connections become unresponsive, and no new connection can be made. This problem only happens infrequently on very high performance servers. In the scenario in which Microsoft was able to reproduce these errors, an SMP computer with fairly high CPU speed was required, and even then this problem only surfaced occasionally.
STATUSMicrosoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words: un-handled AV exception stack overflow link crash
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |