Time out occurred while waiting for buffer latch

Question

Time out occurred while waiting for buffer latch

Viewing 7 posts - 31 through 36 (of 36 total)

You must be logged in to reply to this topic. Login to reply

Morris_Lewis SSC Journeyman Points: 84 More actions · Answer 1

I had both the buffer latch type 2 and I/O timeout errors today. I had about 6 databases that had either data or log files SQL Server could not access, and I failed over the instance to another node thinking that it might be due to a HBA controller or a hard disk going bad. We have an EMC Symmetrix DMX, which has very good error logging, and it reported no errors. There are no hardware errors in the Windows system log either. I went back to the SS logs and found the errors started almost immediately after I installed DK2009 on that server, so it has been removed until DK proves to me they've identified and fixed whatever is wrong. I've seen these kinds of errors just before a database got corrupted, so it seems prudent to err on the side of caution.

harini.hanu Old Hand Points: 385 More actions · Answer 2

hi iam getting this error while executing integrity checks Failed:(-1073548784) Executing the query "DBCC CHECKDB(N'Address', NOINDEX)

" failed with the following error: "Database 0 cannot be autostarted during server shutdown or startup.

The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.

DBCC results for 'Address'

please reply asap

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

Please post new questions in a new thread.

Thanks

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Tim Walker. SSCertifiable Points: 5173 More actions · Answer 4

Just installed Diskeeper 2009 Server 13.0.842.0 .

This was supposed to resolve the matter but in fact SQL Server hung with CPU at 100% after only three hours. A few minutes later it failed over to the passive element of the cluster. No relevant messages in the log this time but I'm convinced Diskeeper was the root case.

Has anybody got a working fix yet?

.

Morris_Lewis SSC Journeyman Points: 84 More actions · Answer 5

Diskeeper support has been good about pursuing this issue, but I've been too busy to get them the relevant logs and other info. If you have not submitted a support request, you should. Having info from multiple sources is going to help them figure out what's going on.

I've pulled Dk2k9 off all my servers until I can get time to resolve it. Since Dk2008 ran fine for months, I'm thinking about downgrading for the handful of servers that really need constant defragmentation.

One other note: watch the server where you had trouble even after you uninstall Dk2k9. I failed over one instance of SS to the node that had trouble, and I had to fail it back less than a week later because of disk I/O errors. There are no errors when it's on the other two nodes, and they never had Dk installed. It may be something specific to the node, but I've no way to tell for sure right now. We're going to wipe it and rebuild it just to get it back to a known-good state.

Tim Walker. SSCertifiable Points: 5173 More actions · Answer 6

Morris_Lewis (4/8/2009)
Diskeeper support has been good about pursuing this issue, but I've been too busy to get them the relevant logs and other info. If you have not submitted a support request, you should. Having info from multiple sources is going to help them figure out what's going on.
I've pulled Dk2k9 off all my servers until I can get time to resolve it. Since Dk2008 ran fine for months, I'm thinking about downgrading for the handful of servers that really need constant defragmentation.
One other note: watch the server where you had trouble even after you uninstall Dk2k9. I failed over one instance of SS to the node that had trouble, and I had to fail it back less than a week later because of disk I/O errors. There are no errors when it's on the other two nodes, and they never had Dk installed. It may be something specific to the node, but I've no way to tell for sure right now. We're going to wipe it and rebuild it just to get it back to a known-good state.

I do have a formal support request in, and I have supplied additional info to Diskeeper. They were pretty sure it was fixed in the release I tried - clearly it wasn't.

Thanks for the advice, I'll keep my eye on it.

.

jake555_1999 SSC Enthusiast Points: 116 More actions · Answer 7

I noticed that you were running into a problem with Diskeeper and your server. The following information should help.

I would install the latest build which is 13.0.844 of Diskeeper 2009. Prior to installing this build, please uninstall the old version completely before installing the new build.

If you still run into problems or need access to this latest build, please call Diskeeper support at (800) 829-6468.