[Veritas-bu] LTO drive won't run at full speed
2003-08-14 17:43:07
This is a multipart message in MIME format.
--=_alternative 00774D9086256D82_=
Content-Type: text/plain; charset="US-ASCII"
veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on 08/14/2003 04:19:53 PM:
> I believe this has been mentioned here before, and I've experienced this
> myself. The LTO drives on our backup system are SCSI connected. On at
> least two occasions, the scsi bus has experienced some kind of
> disruption to cause it to slow down to SE speeds. When I could normally
> get 20+ MB/sec, the affected drive would not write at speeds above 5
> MB/sec. Rebooting the server fixed the problem. If this happens
> frequently, then it's likely a hardware fault. I was able to confirm
> the slowdown by checking the system logs or dmesg. It would clearly
> show the scsi bus error, the devices affected, and would give the exact
> speed or mode that the card was now operating.
>
> -Jon
Same thing happend with our exabyte mammoth drives.
Reboot fixed the problem.
Karl
--=_alternative 00774D9086256D82_=
Content-Type: text/html; charset="US-ASCII"
<br>
<br><font size=2><tt>veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on
08/14/2003
04:19:53 PM:<br>
<br>
> I believe this has been mentioned here before, and I've experienced
this <br>
> myself. The LTO drives on our backup system are SCSI connected.
On at <br>
> least two occasions, the scsi bus has experienced some kind of <br>
> disruption to cause it to slow down to SE speeds. When I could
normally <br>
> get 20+ MB/sec, the affected drive would not write at speeds above
5 <br>
> MB/sec. Rebooting the server fixed the problem. If this
happens <br>
> frequently, then it's likely a hardware fault. I was able to
confirm <br>
> the slowdown by checking the system logs or dmesg. It would
clearly <br>
> show the scsi bus error, the devices affected, and would give the
exact <br>
> speed or mode that the card was now operating.<br>
> <br>
> -Jon<br>
</tt></font>
<br><font size=2><tt>Same thing happend with our exabyte mammoth
drives.</tt></font>
<br>
<br><font size=2><tt>Reboot fixed the problem.</tt></font>
<br>
<br><font size=2><tt>Karl</tt></font>
--=_alternative 00774D9086256D82_=--
|
|
|