Solved!
Go to SolutionRebuild index from suspect damage media
Dear Expert,
i have some problem tapes, by using mminfo i can't see saveset and others information, but while i scanner that tape i founded this error messages.
bpn-nw01_root # scanner -vv /dev/rmt/3cbn
scanner: /dev/rmt/3cbn: opened for reading
scanner: /dev/rmt/3cbn: rewinding
scanner: Rewinding done
scanner: Reading the label...
scanner: Reading the label done
scanner: SYSTEM error: Tape label read for volume ? in pool ?, is not recognised by Networker: Not enough space
scanner: SYSTEM error: Tape label read for volume ? in pool ?, is not recognised by Networker: Not enough space
scanner: scanning for valid records...
scanner: read: 0 bytes
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: -1 bytes : Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: 131072 bytes
scanner: read: 0 bytes
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: -1 bytes : Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: 131072 bytes
scanner: read: 0 bytes
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: -1 bytes : Not enough space
.
.
.
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: -1 bytes : Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: 131072 bytes
scanner: read: 0 bytes
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: -1 bytes : Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: 131072 bytes
scanner: read: 0 bytes
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: 131072 bytes
scanner: read: 131072 bytes
scanner: Found valid record:
scanner: volume id 2884910446
scanner: file number 99
scanner: record number 0
scanner: volume name `BPN199'
scanner: scanning LTO Ultrium-3 tape BPN199 on /dev/rmt/3cbn
scanner: volume id 2884910446 record size 131072
created 10/14/08 14:34:22 expires 10/14/10 14:34:22
scanner: /dev/rmt/3cbn: rewinding
scanner: Rewinding done
scanner: setting position from fn 0, rn 0 to fn 2, rn 0
scanner: /dev/rmt/3cbn: opened for reading
scanner: fn 2 rn 0 read error Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: fn 2 rn 0 read error Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: done with LTO Ultrium-3 tape BPN199
scanner: /dev/rmt/3cbn: rewinding
scanner: Rewinding done
on knowledgebase EMC (as link bellow), explain that problem can fix by third party application, but i don't know how to fix it. is there anyone whose got smiliar problem like this?
https://solutions.emc.com/nsepn/webapps/stqv768481dmts46655278/emcsolutionview.asp?id=esg55944.
Regards
Roud Worde Bedros
i have some problem tapes, by using mminfo i can't see saveset and others information, but while i scanner that tape i founded this error messages.
bpn-nw01_root # scanner -vv /dev/rmt/3cbn
scanner: /dev/rmt/3cbn: opened for reading
scanner: /dev/rmt/3cbn: rewinding
scanner: Rewinding done
scanner: Reading the label...
scanner: Reading the label done
scanner: SYSTEM error: Tape label read for volume ? in pool ?, is not recognised by Networker: Not enough space
scanner: SYSTEM error: Tape label read for volume ? in pool ?, is not recognised by Networker: Not enough space
scanner: scanning for valid records...
scanner: read: 0 bytes
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: -1 bytes : Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: 131072 bytes
scanner: read: 0 bytes
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: -1 bytes : Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: 131072 bytes
scanner: read: 0 bytes
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: -1 bytes : Not enough space
.
.
.
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: -1 bytes : Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: 131072 bytes
scanner: read: 0 bytes
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: -1 bytes : Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: 131072 bytes
scanner: read: 0 bytes
scanner: /dev/rmt/3cbn: opened for reading
scanner: read: 131072 bytes
scanner: read: 131072 bytes
scanner: Found valid record:
scanner: volume id 2884910446
scanner: file number 99
scanner: record number 0
scanner: volume name `BPN199'
scanner: scanning LTO Ultrium-3 tape BPN199 on /dev/rmt/3cbn
scanner: volume id 2884910446 record size 131072
created 10/14/08 14:34:22 expires 10/14/10 14:34:22
scanner: /dev/rmt/3cbn: rewinding
scanner: Rewinding done
scanner: setting position from fn 0, rn 0 to fn 2, rn 0
scanner: /dev/rmt/3cbn: opened for reading
scanner: fn 2 rn 0 read error Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: fn 2 rn 0 read error Not enough space
scanner: /dev/rmt/3cbn: opened for reading
scanner: done with LTO Ultrium-3 tape BPN199
scanner: /dev/rmt/3cbn: rewinding
scanner: Rewinding done
on knowledgebase EMC (as link bellow), explain that problem can fix by third party application, but i don't know how to fix it. is there anyone whose got smiliar problem like this?
https://solutions.emc.com/nsepn/webapps/stqv768481dmts46655278/emcsolutionview.asp?id=esg55944.
Regards
Roud Worde Bedros
- Not enough space is usually triggered by block size problem. It seems as you are trying to read 128KB block, but something is blocking you.
But on second look, it seems it fails to read label as well which is 32KB always which is really really strange. Unless that label has been wiped out by SCSI bus reset I would try to scan this on some other system/device to see if you get the same error. - 7.3.2 is not really nice version of NW. Besides, it is no longer supported for quite some time. 7.3.4 is, but only until March 2009. In 7.4.x corner current version is 7.4.3.2 (aka build 581). You could move to 7.3.4 for start.
As for Solaris, I have no idea what version you have, but if it is supported I see no reason to move on (unless you would gain something from such move). - my experience about networker 7.3.xx are backup performance issue, and we can fix by install new solaris and install new networker 7.3.1. but now it looks strange, is this caused by previous networker version or because hardware problem.
i will start to upgrade networker version 7.3.4 then if not work i will reinstalling solaris, i hope this will work.
Thanks so much for a nice discussion.
Regards
Bedros
Hari5
443 Posts
699
0
Posted November 10th, 2008 16:00