On Thu, 7 Apr 2005, George Sinclair wrote:

>Received the following error:
>
>media emergency: volume version mismatch.
>
>Does anyone know what this means?
>
>Here are the details:
>
>There was a full backup pending (host:/data/dir) and waiting for a
>writable tape. There were no available tapes, so I labeled a new (blank)
>tape (FUL934) in the SDLT 220 drive (/dev/nst4) on our SDLT library
>attached to our storage node server (snode). The tape labeled okay, but
>then NetWorker generated a "Device or resource busy message". At some
>point, it loaded the tape to start writing and then generated the media
>emergency message. After a minute or so, it then loaded it and the
>backup started writing so not sure what's going on. The backup then
>continued where it left off, now writing to the new tape. I don't know
>what this "volume version mismatch" is referring to. As near as I can
>tell, the tape that I labeled does have a unique bar code and was
>labeled with the bar code name. This is not a duplicate volume. There
>are no other volumes with this same name, it was labeled into the
>correct pool, and was never used before. The backup does seem to be
>chugging along just fine. I have provided messages from the server's log
>below.

Perhaps the printed label on that particular tape is smudged.
Does this happen with any other tapes? If so, your tape library's
sensor might be dirty.

--
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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=