Networker

Re: [Networker] HELP - media errors after update NW6 -> NW7

2005-08-01 11:21:22
Subject: Re: [Networker] HELP - media errors after update NW6 -> NW7
From: Darren Dunham <ddunham AT TAOS DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 1 Aug 2005 08:18:15 -0700
> But this is not the problem, even auto-recycling fails:
> 
> 08/01/05 16:59:11 nsrd: nsrjb notice: nsrjb -j L700e -O15 -l -R -M 000191
> 08/01/05 16:59:21 nsrd: media info: loading volume 000191 into /dev/nst2
> 08/01/05 16:59:38 nsrd: /dev/nst2 Verify label operation in progress
> 08/01/05 17:00:09 nsrd: media warning: /dev/nst2 reading: Success
> 08/01/05 17:00:21 nsrd: media warning: /dev/nst2 reading: no tape label found

That looks like the problem there....

> 08/01/05 17:00:21 nsrd: /dev/nst2 Eject operation in progress
> 08/01/05 17:00:51 nsrd: Jukebox 'L700e' failed: expected volume '000191' got 
> 'NULL'.

Since it can't verify that *this* is 000191, it has to assume that
'000191' still exists elsewhere.  It can't give that label to this tape,
or you'd potentially have two of them.

It can only reassign when it knows it's overwriting the original copy,
and that can only happen if it can verify the label on the tape.

If you're sure that this is in fact the other copy, you can delete it
from the database.  However, I might be interested in why the label is
unreadable.


> [several volumes later]
> 
> 08/01/05 17:02:21 nsrd: media info: loading volume 000146 into /dev/nst3
> 08/01/05 17:02:37 nsrd: /dev/nst3 Verify label operation in progress
> 08/01/05 17:02:58 nsrd: /dev/nst3 Label without mount operation in progress
> 08/01/05 17:02:59 nsrd: media info: LTO Ultrium tape 000146 will be 
> over-written
> 08/01/05 17:02:59 nsrd: deleted media notice: Deleted volume: 
> volid=2903745281, volname=000146, location=L700e
> 08/01/05 17:03:25 nsrd: /dev/nst3 is now enabled read/write
> 08/01/05 17:03:25 nsrd: /dev/nst3 Mount operation in progress
> 08/01/05 17:03:26 nsrd: media event cleared: Waiting for 1 writable volumes
> 
> 
> Could it be that this is a bug? Hmm, I will delete the jukebox and 
> reconfigure it.

I doubt that this has *anything* to do with your jukebox configuration.

Most of my label failures have to do with the old label failing to
verify, or with the jukebox device "reading" the wrong information for
the barcode (like reading a complete blank or "000000" instead).



-- 
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. >

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