Hi,
With networker 7.3.2, the mminfo query "full" don't return any match.
You can find this example in the command reference guide (or in man page of mminfo):
"Display a media report of all non-full volumes, showing the percent-used, pool and location of each volume: mminfo -a -r...
Finally, the networker solution will be re-install, because too many problems : one month ago, when the administrator move the networker server from Tru64 to Linux OS, he just copy the nsr directory to the new machine !
Many thanks
Thanks, The device block size is set to variable (0).
I don't know how to set block size in Linux, because the stinit.def is not loading in the system. Do you have an idee ?
Hello,
No problem, CDI is disabled. We have mount and unmount 40 different tapes from the librarie, and the 41ers was read without problem ! All this tapes were writing when the Networker server was running on Solaris.
Now all seems to be running well but we always have those messages in the...
2 other drives failed with the same error message.
But the dmesg from Linux gives some errors like : st3:
Error with sense data: Info fld=0x0, Current st3: sense key Medium Error
Additional sense: Write error
st3: Error on write filemark...
OS can't speak correctly with drive.
With a new tape, networker is unable to label it.
It's the same error with any tapes.
All drives in L700 jukebox are Quantum SDLT320.
Just a strange thing : last week mt -f status on the drive give :
root@usu>mt -f /dev/nst4 status
SCSI 2 tape drive:
File number=-1, block number=-1...
Many thanks for your answer,
Here is the result of scanner (no error with mt -f status) :
root@usu>nsrjb -lnv -S 677 -f /dev/nst4
setting verbosity level to `1'
nsrjb: Info: Loading volume `-' from slot `677' into device `/dev/nst4'.
root@usu>scanner -v /dev/nst4
scanner: /dev/nst4: opened...
Hello,
After adding a new SDLT320 drive in jukebox L700, networker load a volume in this drive, but label verification fails on this error :
nsrd: /dev/nst4 Verify label operation in progress
nsrmmd #6: tape_bsf bsf failed: drive status is The drive is not ready and the reason is not known...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.