Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Serious problem with scanner command 3

Status
Not open for further replies.

riccapocci

Technical User
Nov 22, 2002
2
IT
Hi admins!
I've a serious problem with scanner command on my Legato server (Solaris 7, Legato 6.1). Since yesterday, when I try to scan a volume, I get the following message:

# scanner -i /dev/rmt/6mbn
scanner: scanning 9840 tape 002276 on /dev/rmt/6mbn
scanner: fn 2 rn 0 read error Not enough space
scanner: fn 2 rn 0 read error Not enough space
scanner: done with 9840 tape 002276

and consequently the media and index database for this volume are not rebuilt. Did anybody see that before?

Any suggestion would be appreciated.

Thanks in advance.




 
Never seen that myself. What I would do is this...

dd off the header of a known-good tape (preferably from the same pool)

dd off the header of that tape

compare the two to see if they are relatively similar.

That's just my first idea. I'm sure there are better ones, but I'm not familiar with potential problems with Networker on Solaris.
 
How old is this tape?

There are a number of things that could be causing this error:

1. block size used for writing is different from block size used for reading

2. 9840 drive is not set up in the /kernel/drv/st.conf

3. you may need a patch from sun for 9840 drives. Goto sunsolve.sun.com and search for 9840.
 
Thanks a lot.
Our problem is related to ALL our volumes.
Backup and recover work correctly; only the scanner command fails on all volumes and on all our four drives.
It's the first time that scanner doesn't work: we did the last volume scan just two weeks ago.

Thanks a lot for your suggestions... do you have any other?

 
try running scanner -vvv and then any other parameters you are using.
This will report the blocksize of the backup.

Look at running scanner -m instead of scanner -i (assuming you are running scanner -i) to see if it is a problem with the client indexes only, as opposed to the media index.

Lastly, do you actually have plenty of space free where the indexes are held?
 
scanner: fn 2 rn 0 read error Not enough space

tells me that it choked tryig to read the beginning of the tape. (fn=File number). As TDun suggested, use scanner -vvv to see if there is any valid label and data on that tape.


I would check to see if the scanner command itself is the same 6.1 version. For example:

# /usr/ccs/bin/what /usr/sbin/scanner
/usr/sbin/scanner:
Build info:
Build arch.: solaris
Build date: Thu Nov 21 18:00:12 PST 2002
Build number: 428
Release: 6.1.3.Build.428
Product: NetWorker
SunOS 5.5.1 Generic May 1996

If it shows a different version that what you expect (6.1) then you cound have a binary problem. Run pkginfo | grep -i lgto to see what has been installed


Since you are using 6.1... there could be a bug in the scanner command itself. Upgrading to 6.1.3 would be a good
idea in any case.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top