Same here , I wrote my own fill program though,

but even if my fill program fills it and reads back all the data proper
all I can see is that same tapes have speed problems and do not always go to
the full 200 gb that LTO-2 should.

Networkers (sometimes) faults on them anyway after that

By the way the tests are done on the same machine as legato.

maarten

On Thursday 05 August 2004 14:55, Reed, Irene wrote:
> I have done it all.  I took an erroring tape and removed it from legato.
> Tarred over the legato lablel.  Tarred over the entire tape with a tool
> legato gave me (fill) to send data to it and verify how much data would
> fit and how fast it would write to it.  This worked fine.  I labeled the
> tape back into Legato.  I verified the label was 64k.  I then let Legato
> use it and I had I/O errors on it and it wrote the tape full
> prematurely.  Go figure?
>
> Irene
>
> -----Original Message-----
> From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT 
> EDU]
> On Behalf Of Eichelberger, Jon
> Sent: Thursday, August 05, 2004 7:50 AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] LTO drive problems after upgrade to NW 7.1
>
> Hi, All.
>
> I have not made it all the way through the thread on this,
> but has anyone put one of the erring tapes in an erring drive and just
> tried to write on it/beat the heck out of it with tar or
> whatever, thus getting Networker out of the loop?
>
> I'm sure you'll have to prove this is not a drive/media issue
> before Legato will give you help, despite what any Legato
> employees monitoring this discussion might say.  Legato's
> position could be that an earlier version of Networker was
> letting errors slide by and that the newer version is "correctly"
> exposing these.
>
> If nothing else, I am hoping what I am saying is stirring the pot
> to bring this issue to a boil and get it fixed.  Since I make software
> and hardware decisions for my company in regard to the backup landscape,
> I cannot consider deploying LTO with Networker 7.x until this is
> resolved.
> I have used Networker 6.1.3 on Solaris 8 with LTO-2 with zero issues.  I
> guess I
> will not be updating.
>
> Jon
>
> -----Original Message-----
> From: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]On Behalf Of Gilles, Paul
> Sent: Thursday, August 05, 2004 12:44 AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] LTO drive problems after upgrade to NW 7.1
>
>
> I am seeing the same recurring problem. Approximately, every two days,
> the
> tape devices are unable to be used, giving I/O errors. The only solution
> is
> to reboot the Legato server. It's almost like a counter is being filled,
> but
> the error counters on the tape drives are not full. We do get a lot of
> tape
> critical warnings because we don't have sufficient tape drives, so the
> backup groups wait a while for a free tape drive.
>
> Legato 7.1 is running on a Sun V480 with Solaris 9. The tape library is
> an
> ADIC i2000 with 7 IBM LTO-2 drives. They are fibre-channel connected via
> a
> SAN through a CISCO 9509 with a Hitachi 9580 disks.
>
> Paul Gilles
> Systems Administration
> NAVTEQ
>
> >Date:    Wed, 4 Aug 2004 19:01:08 +0300
> >From:    Itzik Meirson <imeirson AT MBI.CO DOT IL>
> >Subject: LTO drive problems after upgrade to NW 7.1
> >
> >It seems that we are experiencing som LTO instability after upgrading
>
> fro=
>
> >m Networker 6.1.x to 7.1.x.
> >It seems as if after the upgrade we are getting very sporadic tape I/O
>
> er=
>
> >rors that are causing premature tape closure. We have tried to disable
>
> CD=
>
> >I but that did not realy solve the problem.
> >I wonder if any of you have seen such problems and could recommend a
>
> proc=
>
> >edure to solve the problem.
> >Itzik
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Maarten Boot,
Compuware Europe B.V.
Hoogoorddreef 5
1101 BA Amsterdam

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=