Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1157
  • Last Modified:

Error: dstartio: I/O request repeatedly delayed

Hi,

    Here's a few errors I got from my Sybase's log.
block number: 30451, vdn: 3
00:00000:00000:1999/01/21 13:09:22.39 kernel  dstartio: I/O request repeatedly delayed;
and it's repeated ... many times. It happend mostly when I do some bcp into my database. Could someone point me into the right direction as what might have cause it and the fixe ?
0
n0thing
Asked:
n0thing
  • 3
1 Solution
 
david_levineCommented:
I found the following post on DejaNews. It was posted by someone with your issue and is a response from Sybase to that person.

The dstartio error you're seeing is often caused by unequal rates of asynchronous i/o between the server and the operating system.  This is informational, sometimes indicates some small performance degradation, but unless you're seeing a huge amount of them, it can safely be ignored.  In most cases, changing three configuration parameters clears up the problem,
so I'd like you to try this, please:  set to 500 the following parameters:
disk i/o structures, max async i/os per server, and max async i/os perengine.

For reference, there's an excellent writeup (although rather well-hidden) in the back of the Error Messages manual.  It's titled "Dstart I/O Request Repeatedly Delayed", and does have an index entry for the page number.

0
 
n0thingAuthor Commented:
I've reconfigure the server with the sync I/O and other parameters. Seems to be working fine right now. I didn't see your
comment. However it points to the right direction. Would you mind posting an empty answer so I could give you the points ??
Regards,
Minh Lai
0
 
david_levineCommented:
Glad you seem to be running!
0
 
syeatsCommented:
Hi, just joined this site.
I'm having the same problem with the third dataserver on a Sun box
I've set the 3 parameters you mention to 100, but still get the errors.
The Sybase doco says not to configure maxasync i/os per server higher than 200 for versions of Solaris 2.4 or higher.
Why do you recommend 500?
Regards,
Simon Yeats.
0
 
david_levineCommented:
Sorry, I don't know what you should do in your case. I found the answer I posted by searching the net. It helped the person whose problem seemed to match the one I found.

David
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now