I should have mentioned that I did check to see if the database had that
volid. It does not. The result of the command is just the header line:
volume barcode
I am not aware of ever having forced any tapes to become recycleable.
>From time to time I do change some tapes to manual recycle via the GUI,
and I do sometimes relabel tapes, but this was NOT one of those -- at
least not that I'm aware of or can recall.
So steps to carry out should be:
1. nsrck -mv
2. nsrck -Xv
3. Delete volume
4. nsrck -mv
5. nsrck -Xv
6. Scan tape using scanner -m <drive> or scanner -i <drive>?
Just kinda has me worried that maybe scanning in the data might screw up
something in the online file indexes? Then again, maybe not since none
of the reported ssids show up anyway. But, here's a question. The last
part of the output from the scan I ran earlier (scanner -inv <drive>)
indicated that one of the savesets continued on another tape, so if I
scan in the data on this trouble tape then it might ask for that next
volume, but how do I know what volume that is? It gave me an ssid for
the saveset, but that ssid doesn't show up in the database, so I can't
very well figure out what volume it would be on so wouldn't know which
volume to load?
Thanks.
George
Tim Mooney wrote:
>
> In regard to: [Networker] Problem child tape -- what to do???, George...:
>
> >1. Output from: mminfo -aq 'volume=volume_name' shows this volume as
> >having 7 savesets. No problems here. Whether we believe it or not is another
> >matter.
>
> What does
>
> mminfo -q volid=606471681 -r 'volume,barcode'
>
> report?
>
> >I'm beginning to wonder if the on-line file index entries for the data
> >on this tape is just completely bogus -- as in it matches some other
> >volume and not this one,
>
> My suspicion is that is indeed the case. My guess is the mystery volume
> is one that you forced into the recycleable state, using either the
> GUI or nsrmm.
>
> > or maybe it's just a fantasy. Or, is it
> >instead the other other way around? I guess I was planning to rebuild
> >just the media database by running: scanner -m <drive> but at least
> >one person suggested maybe deleting the volume first.
>
> I would recommend doing that too (delete the volume), but see below.
>
> > If I do that,
> >however, then won't the file indexes get wiped out, too?
>
> Yes, but that may not be a bad thing.
>
> You should probably run a consistency check both before and after you
> do anything with that volume (i.e. delete it). You might want to do
> something like
>
> nsrck -mv
> nsrck -Xv # aka nsrck -v -L 3
>
> The burning question I have is this: Have you manually (either via
> the GUI or nsrmm) forced any tapes to become recycleable recently?
>
> Tim
> --
> Tim Mooney mooney AT dogbert.cc.ndsu.NoDak DOT
> edu
> Information Technology Services (701) 231-1076 (Voice)
> Room 242-J6, IACC Building (701) 231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
