October 7, 2010 at 1:16 pm
experiencing a rash of QL2300 errors across WINTEL / Linux and vm platforms over last two days- no changes have been performed to indicate a common source . . . drivers have not changed in past few days, and have been running for at least a year...ideas?
October 7, 2010 at 1:36 pm
Eh?
What's a QL2300 error? What's the message? What's the context?
Honestly I don't have a clue what you're asking. If you want some useful help, I think you're going to have to give a lot more details for the problem.
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
October 7, 2010 at 2:05 pm
Are you running QLogic 2300 fibre channel cards?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
October 7, 2010 at 2:19 pm
An SQLServer forum seems a bit of a crazy place to ask for help with a problem with a fibre-channel card (or its driver), particularly when the error is occurring on Linux and VM platforms as well as on Windows.
You are not going to get useful answers anwhere if you don't give a bit of information about the errors: for example for the Windows platform(s) what are the event IDs in the event log, how do the errors manifest themselves, what is the hardware platform.
As it's happening on Linux and VM and Windows, it's probably in the card or in the SAN controller or in the server's interrupt control hardware or in some very low level component of the driver or the fibre-channel protocol stack (low enough to be in firmware) - anything higher up the tree than that is not going to be common to completely different operating systems. If as you say nothing has changed I would guess something may have joggled the card (sometimes cleaners accidentally do this) - so checking the card is properly seated, checking that the fibre is correcly aligned to the emitters and receivers, and other absolutely basic hardware checks may find it - or the card may have failed.
If the errors are recoverable and are not reducing throughput enough to matter, you should take them as a warning that some component has begun to fail (just like single bit errors logged on decent RAM) and think about replacing it.
Tom
October 7, 2010 at 2:41 pm
All I can tell ya is if you have a rash, don't scratch...
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply