UNSOLVED
TAR on EDL embeded storage node
We are implementing embeded storage node for Networker on an EDL 4100 to be clone storage node. There are 8 LTO-4 Tapedrives connected to EDL ports which are a part of a library connected to NW Server.
-The EDL devices are configured and working fine emulating LTO-4 drives.
-LTO-4 devices are also connected and seen from inquire command.
-I am able to load tapes in the LTO-4 tapes throught the NW Gui (Jukebox is physically controlled by Legato Server)
-mt -f /dev/nstX status works fine
-tar hangs.
-Tapes can be mounted but cannot be labeled.
- lsmod command shows the st driver loaded
I am new to Linux but I guess that the OS is not talking to the Tape drives.
I believe that if tar works, NW will also be able to label tapes etc.
Has anyone seen this, any ideas on how to make tar work on this ?
Thanks.
-The EDL devices are configured and working fine emulating LTO-4 drives.
-LTO-4 devices are also connected and seen from inquire command.
-I am able to load tapes in the LTO-4 tapes throught the NW Gui (Jukebox is physically controlled by Legato Server)
-mt -f /dev/nstX status works fine
-tar hangs.
-Tapes can be mounted but cannot be labeled.
- lsmod command shows the st driver loaded
I am new to Linux but I guess that the OS is not talking to the Tape drives.
I believe that if tar works, NW will also be able to label tapes etc.
Has anyone seen this, any ideas on how to make tar work on this ?
Thanks.
- -If we try to label using NetWorker it hangs on labelling for about an hour and errors out saying "i/o error, unable to read"
- No errors on CDL console, remember these taopes drives show up in the EDL: console but are not controlled by EDL software. EDL comes with an embeded storage node for networker option which is supposed to work exactly like any linux storage node.
-I am guessing tapes are not labelled by networker because of the i/o errors which is possibly the cause of tar failure as well.
Thanks in advance. - I understand that EDL is not controlling the tape library but as the EDL is going to be working as a sn, any hardware errors are likely to show up on the EDL not on the NW server. In any case, the i/o errors are in all probability the root cause. You might want to have the physical tape drives hardware checked as a problem there could be causing your errors. I am presuming that the tape media itself is alright.
Hari5
443 Posts
272
0
Posted February 10th, 2009 23:00