As I understand the problem you had instructed networker to load TAPE1 on some
drive, then you ran scanner on that drive expecting to see TAPE1 and its
contents but scanner found a different label (and hence a different tape)
You did not explain if we are talking about barcodes and a "match barcode"
configuration...
I suspect a device order problem here (either at scanner time or at labeling
time).
The device (dis)order situation may not be there anymore but the consequences
could be permanent (e.g. tape crosslabeling).
If I got that right, then I suggest to check the device order using the
following commands:
[1] inquire
[2] sjisn [email protected]
(B.T.L is the SCSI address the robotic arm as shown by inquire)
[3] nsrjb
[1] and [2] should provide the current device mapping (use the serial number
as the index that provides the device order).
Compare this device mapping with the one configured in networker which should
appear at the end of the nsrjb output [3].
The combination of inquire+sjisn should be in sync with the device order shown
by nsrjb, otherwise if you instructed NW to mount TAPE1 on some drive the
tape would actually be mounted somewhere else (because the OS would be
mapping the drives differently). As a consequence you would get either an
error like "expected tape XXXXXL got YYYYYY" or "...got NULL".
This check should be done at the time when the problem is happening. If you
run this check at some other time and the device order has been reestablished
(maybe after a new reboot), then you may get confused. However it is always
handy to check and see the current mapping of drives and compare it to the NW
configuration (nsrjb) so you know where you are.
Example of device order problem
Monday:
sjisn shows the following drive order are in the jukebox:
drive 1: SN: XXX1
drive 2: SN: XXX2
Inquire may show that /dev/rmt/0cbn corresponds to the drive with Serial
Number: XXX1 and /dev/rmt/1cbn to the drive with Serial Number: XXX2.
When you configure NW the device order is
drive 1: /dev/rmt/0cbn
drive 2: /dev/rmt/1cbn
Tuesday:
After a reboot or some changes on the SAN, you end up with the following
configuration:
/dev/rmt/0cbn now mapped to SN: XXX2
/dev/rmt/1cbn now mapped to SN: XXX1
So, on Tuesday, when you ask NW to load TAPE1 on /dev/rmt/1cbn, NW looks at
its own configuration (the one created on Monday) and finds
that /dev/rmt/1cbn is "drive 2". With this information, NW instructs the
robotic arm to mount TAPE1 on the *second* drive of the jukebox.
=> The problem here is that the second drive on the jukebox (i.e the one with
SN: XXX2) is now **mapped** to /dev/rmt/0cbn by the OS but NW doesn't know
that and mounts the tape on the wrong OS drive.
If you happened to have some other tape already mounted on the *other* drive
(i.e. /dev/rmt/1cbn ) then networker would read the label of the other tape.
Why? because nsrmmd is definitely using the drive "/dev/rmt/1cbn". It
doesn't know about robotic arms and drive order. It only knows
about /dev/rmt/ entries (when the device driver "opens" the /dev entry, it
gets a handle for the current physical device which is the first one now)
using sjisn+inquire and additionally sjimm and/or sjirdtag should help in this
kind of situations because you would know where the tapes actually are.
jee
On Tuesday 21 July 2009 4:27:39 pm Stranger wrote:
> Hello folks,
>
> I have a very strange problem.
>
> When I run /usr/sbin/nsr/mminfo -m command, I get name of the tape TAPE1
> and information that it's empty and does not contain any data.
>
> when I run /usr/sbin/nsr/scanner -B /dev/rmt/0cbn command, I get the
> information that it's TAPE2.
>
> Did anyone meet something like this and know what can lead to it ?
>
> thanks in advance
>
> +----------------------------------------------------------------------
>
> |This was sent by igorzet AT gmail DOT com via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
>
> +----------------------------------------------------------------------
>
> 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
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
|
