Hi,
I'm having some problems with a particular volume. I posted an earlier
message
concerning my inability to mount this tape, and indeed it was a case of
the volid
for that tape not matching the one that NetWorker had in its database
(THANK YOU ALL!!!!), but now there are some additional problems as I
will
explain, and I have some questions on how best to proceed.
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.
2. When I ran the scanner command to scan the tape to obtain its
volid, I ran it as: scanner -inv <drive> and saved the output to a
file (sample output included below). I then went in to look at the
contents, and I noticed several
interesting things. First, among all the voluminous output, there were
5 different ssids reported, but 99.9% of the file refers to only three
of them, and so there are only a few places where the other 2 are
referenced. None of the 5 lists in the database. I ran mminfo -aq
'ssid=ssid_number' for each and none turned up! The other interesting
thing is that none of these ssids match any of the ssids reported in
item 1 above! One of the two ssids that's only reported a few times
corresponds to a file system that wasn't even reported in 1
above. There are also some error messages near the end of the
file. Also, near the end, it reports that there is a continued saveset
on another tape, and it reports the file system and the ssid, but this
file system again is not one of the 7 listed in item 1, and I checked
for the ssid and it's not listed in the database either. I've provided
a sample output below.
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, 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. If I do that,
however, then won't the file indexes get wiped out, too? Seems then
that I would need to run scanner -i to rebuild both, but I'm thinking
maybe I don't wanna do that based on some of the error messages ... I
mean
maybe that might end up corrupting some of the valid online file index
information. Maybe just rebuild media database and not delete volume
first? Something else?
Thanks.
George
########## sample output from scanner -inv <drive> ##############
scanner: Rewinding done
scanner: Reading the label...
scanner: Reading the label done
scanner: scanning sdlt tape FUL649 on rd=snode:/dev/nst4
scanner: volume id 606471681 record size 131072
created 2/06/04 23:40:54 expires 2/05/06 23:40:54
scanner: adding sdlt tape FUL649 to pool FUL
scanner: Rewinding...
scanner: Rewinding done
scanner: setting position from fn 0, rn 0 to fn 2, rn 0
scanner: Opened /dev/nst4 for read
scanner: scanning file 2, record 0
scanner: ssid 1093753601: continued from `FUL631', scan for
synchronization
scanner: ssid 1093483009: continued from `FUL631', scan for
synchronization
scanner: ssid 1093463041: continued from `FUL631', scan for
synchronization
scanner: ssid 1093753601: SYNCHRONIZED at 40 GB, 135948 file(s)
scanner: ssid 1093463041: SYNCHRONIZED at 50 GB, 478705 file(s)
scanner: scanning file 2, record 100
blah-blah-blah
scanner: Opened /dev/nst4 for read
scanner: scanning file 72, record 0
scanner: ssid 1093463041: 93 GB, 771443 file(s)
scanner: scanning file 72, record 100
scanner: scanning file 72, record 200
scanner: scanning file 72, record 300
scanner: scanning file 72, record 400
scanner: scanning file 72, record 500
scanner: fn 72 rn 506 read error Input/output error
scanner: Opened /dev/nst4 for read
scanner: fn 73 rn 0 read error Input/output error
scanner: Opened /dev/nst4 for read
scanner: fn 73 rn 0 read error Input/output error
scanner: Opened /dev/nst4 for read
scanner: ssid 1093463041: NOT complete
scanner: ssid 1093463041: 93 GB, 771443 file(s)
scanner: done with sdlt tape FUL649
scanner: Rewinding...
scanner: Rewinding done
scanner: the following save sets continue on another volume:
client name save set save time level size files
ssid S
client1 /raid 2/29/04 0:00 f 95378219156 771443
1093463041 S
scanner: when next volume is ready, enter device name (or `q' to quit)
[rd=snode:/dev/nst4]?q
scanner: (ssid 1093463041) error decoding save stream
scanner: (ssid 1093463041) would have added 293506 new file index
entries
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
