At what point can I blame the storage?

I quite often find myself wishing a problem would go away. I get desperate to hand off the whole thing to, say, a SAN engineer and be done with it. At what point then is it possible, when troubleshooting poor storage latency,  to do this?

Say i’m looking at some pretty shoddy secs/write on a LUN. I can say to the storage guy “i don’t like your storage”. He then tells me that the secs/transaction he sees are fine. Is there any way to get just a little bit more info out of the box to narrow down the problem (or slope my shoulders just a little bit more?)?

yes there is.

http://blogs.msdn.com/b/ntdebugging/archive/2010/04/22/etw-storport.aspx

As far as i can make out, if you follow that article you can get a measure of how long it takes the storport driver to get a response from EVERYTHING ELSE. So, if you’re seeing 50ms/read in the perfmon, but it never goes above 30ms to service a request, you might want to make sure you’ve got the latest version of storport on your system. Conversely if (like me) you’re seeing 500ms request times in storport, you get together with Mr Storage and go yell at the network elves.

Advertisements
Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: