November 1, 2007 at 4:57 am
we keep seeing these entries in the logs of several sql 2005 servers A time-out occurred while waiting for buffer latch -- type 2, bp 02D734C0, page 1:6156898, stat 0x1c0040d, database id: 7, allocation unit Id: 72057594073251840, task 0x0091F1F8 : 2, waittime 300, flags 0x3a, owning task 0x00918E38. Not continuing to wait.'
This is causing major problems but I'm at a loss. The affected servers are all on the same disk group in the SAN and and several different proccesses are failing round about the same time with this error.
Any Ideas??
November 1, 2007 at 7:21 am
These types of errors suggest that the disk subsystem is unable to keep up with the level of I/O MSSQL is asking. MSSQL waits and retries these requests. These errors may also indicate that the disk subsystem is experiencing problems - check event log for hardware errors, check the SAN for failed/degraded drives.
Tommy
Follow @sqlscribeNovember 1, 2007 at 9:34 pm
Don't forget to have the storage folks take a look at fabric switches as well, if only some of your servers are affected while others are just fine, look for the common element (e.g. a common switch, uplink, etc.)
November 1, 2007 at 11:24 pm
This is an IO error possibly due to a corruption in the physical disk. You need to get this cleared using some tools so that the IO error is rectified.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply