[337] in Athena_Backup_System
Re: Curious
daemon@ATHENA.MIT.EDU (delgado@MIT.EDU)
Fri Oct 25 12:57:47 1996
From: delgado@MIT.EDU
To: ted@MIT.EDU
Cc: athena-backup@MIT.EDU
In-Reply-To: Your message of "Fri, 25 Oct 1996 12:11:41 EDT."
<9610251611.AA04187@chaos.MIT.EDU>
Date: Fri, 25 Oct 1996 12:57:40 EDT
It is actually not reporting all types.
The weirdness is a side effect of the auto-labeling feature.
When a tape is auto-labeled by a slave, the following things happen:
- the slave requests the master to generate an external/internal label id pair
- The master generates the external/internal id for the new tape and inserts
it into the database. The new tape's status is set to "unlabeled", since
the tape has not been physically labeled yet.
- The slave labels the tape and continues dumping.
- The slave finishes the dump and reports its results to the master.
- If the dump is successful, the master sets the new tape's status to VALID.
- If the dump is not successfull, nothing is updated - not even the
new tape's status. This is because we don't really know whether the
label was successful.
In this case the administrator should go into the abs ui and issue:
% showmed -po xb1
Media ID Media Pool Status Error
xb1-0003 xb1 VALID 0
xb1-0002 xb1 FREE 0
xb1-0001 xb1 UNLABELED 0
This lists the status for all tapes in the pool. The administrator
can delete the "UNLABELED" tape from the pool, if he is certain that
this tape isn't really being used by any executing jobs.
We don't do automatic deletion after the end of a job because there
is no information maintained regarding the job which requested the
auto tape label and the tape in the "unlabeled" state. (i.e., we
could inadvertently delete "unlabeled" tapes which are actually
being used by other jobs"
I will fix the abs to report counts for all tapes, including "unlabeled".
Thanks,
dmd
