SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
volume version mismatch?
Author Message
Post volume version mismatch? 
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.

Would appreciate any input.

Thanks.

George


Here are the last entries from the server's /nsr/logs/daemon.log

04/07/05 09:59:25 AM nsrd: rd=snode:/dev/nst4 Verify label operation in
progress
04/07/05 09:59:57 AM nsrd: media warning: rd=snode:/dev/nst4 reading:
Input/output error
04/07/05 09:59:58 AM nsrd: media warning: rd=snode:/dev/nst4 reading:
Tape label read: Input/output error
04/07/05 10:00:05 AM nsrd: nsrjb notice: nsrjb -s server -j
rd=snode:SDLT -Y -O42 -L -g -bFUL -f rd=snode:/dev/nst4 -S 6
04/07/05 10:00:07 AM nsrd: rd=snode:/dev/nst4 Verify label operation in
progress
04/07/05 10:00:09 AM nsrd: media warning: rd=snode:/dev/nst4 reading:
Input/output error
04/07/05 10:00:10 AM nsrd: media warning: rd=snode:/dev/nst4 reading:
Tape label read: Input/output error
04/07/05 10:00:13 AM nsrd: rd=snode:/dev/nst4 Label without mount
operation in progress
04/07/05 10:01:10 AM nsrd: rd=snode:/dev/nst4 Eject operation in
progress
04/07/05 10:01:13 AM nsrd: media info: suggest mounting FUL934 on snode
for writing to pool 'FUL'
04/07/05 10:03:39 AM nsrd: media info: loading volume FUL934 into
rd=snode:/dev/nst4
04/07/05 10:04:17 AM nsrd: rd=snode:/dev/nst4 Verify label operation in
progress
04/07/05 10:08:18 AM nsrd: media warning: rd=snode:/dev/nst4 opening:
Device or resource busy
04/07/05 10:08:19 AM nsrd: media warning: rd=snode:/dev/nst4 reading:
read open error, Device or resource busy
04/07/05 10:08:23 AM nsrd: rd=snode:/dev/nst4 Eject operation in
progress
04/07/05 10:12:23 AM nsrd: media warning: rd=snode:/dev/nst4 opening:
Device or resource busy
04/07/05 10:14:56 AM nsrd: rd=snode:/dev/nst2 Eject operation in
progress
04/07/05 10:16:54 AM nsrd: media info: loading volume FUL934 into
rd=snode:/dev/nst4
04/07/05 10:17:32 AM nsrd: rd=snode:/dev/nst4 Verify label operation in
progress
04/07/05 10:17:39 AM nsrd: rd=snode:/dev/nst4 is now write enabled
04/07/05 10:17:39 AM nsrd: rd=snode:/dev/nst4 Mount operation in
progress
04/07/05 10:17:46 AM nsrd: media event cleared: Waiting for 1 writable
volumes to backup pool 'FUL' tape(s) on snode
04/07/05 10:17:46 AM nsrd: media emergency: volume version mismatch
04/07/05 10:17:51 AM nsrd: host:/data/dir saving to pool 'FUL' (FUL934)
95 GB

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Post volume version mismatch? 
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.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Post volume version mismatch? 
On Thu, 7 Apr 2005, George Sinclair wrote:

When you say printed label, I assume you mean the actual bar code label
itself and not the internal label that NetWorker writes to the magnetic
media, correct?

Yes. That's what I meant.

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Post volume version mismatch? 
When you say printed label, I assume you mean the actual bar code label
itself and not the internal label that NetWorker writes to the magnetic
media, correct?

I have seen this happen a few other times. I have "Bar code reader" and
"Match bar code labels" set to 'yes' when labeling tapes with these bar
codes.

Thanks.

George

Stan Horwitz wrote:

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.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB