> we had this once and we couldn't fix it.
> This was Legato 7.1.1 / Windows 2003 /HP ESL 9000 / SDLT.
> 
> If i remember correctly, this could happen if the Label couldn't 
> be written to tape, as Legato removes the Tape from the media DB
> before relabeling. When Verifing the Label, it's reading the old
> Label, as the Label couldn't be written, resulting in a "dublicate
> Label.

No, the error comes before an attempt is made to write the new label.
When it's ready to write to the tape, it tries to allocate the name in
the media database.  At that point, it discovers that the conflict.

So this could happen if the *old* label couldn't be read (because then
it wouldn't know that this is the old tape and that it can delete the
media information).  It would think it was trying to create the same
name on a new tape instead of recycling.

-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER