n
n
Avid Composer Products Software Has Performance Issues
Avid Disk Error Analyzer Showing the New Errors
What to Do When You See the New Errors
When viewing the new errors you need to determine if you need to replace the
disk reporting the errors. You should use the following explanations as a
guide:
•
Long Read or Write Command Times - A block is rewritten whenever
there is a long read or write. This has been shown to resolve the issue in
many cases. Therefore, the occasional long read or long write can be
safely ignored. However, if you see a disk that is reporting more that three
long command times in a week, it should be replaced.
It is possible that once a long I/O happens, other requests to that drive are
also held off with a long I/O message. Make sure that the three long I/Os over
the week are separate long I/Os, and not just multiple reports of the same long
I/O from the same drive.
•
STATUS_IO_DEVICE_ERROR - This is a serious hardware error and
the disk should be replaced.
If you take the disk offline from the controller manually, you might see the
STATUS_IO_DEVICE_ERROR error.
Problem: The Avid Composer Products application you are running is
performing slowly or, potentially, not running.
Possible Cause: The LANserver EX3 and the client with the performance
problems are not on the same subnet mask, forcing the data to go through
additional routing while being transferred between the two systems. If the data
transfer is slow enough, it can cause the Avid Composer Products application
to perform poorly or to stop functioning.
Data transfer between the LANserver EX3 and its clients must occur directly.
You can use the tracert utility to verify whether or not the data transfer uses a
direct, optimal path. See
Troubleshooting a LANshare Workgroup
"tracert" on page 69
for more information.
77
Need help?
Do you have a question about the Unity LANserver EX3 and is the answer not in the manual?
Questions and answers