We have a tape library which is connected to a server by SAS link. Server is running OS Linux. OS doesn't see the tape library in /proc/scsi/scsi . We tried to rescan scsi bus(*1), but it didn't help.
What could we do to access it?
PS:The main goal is just to see it connected to the server We also have storage system connected to the same HBA. Servers,storage and library vendor - HP.
*1 - for each host we run echo '- - -' > /sys/class/scsi_host/hostN/scan
I have an executable which needs to link with libtest.so dynamically,so I put them in the same directory,then :
cd path_to_dir
./binary
But got this:
error while loading shared libraries: libtest.so: cannot open shared object file: No such file or directory
How can it be unable to find libtest.so which is already in the same directory as the executable itself?
I need to figure out if I can get this to work. I have a HP P2000 Storage system, connected to 2 x HP DL360 G7 through SAS. Then I got an HP Autoloader with connected through SAS too.
Will I, in ESXi 4.1, be able to mount both the tapedrive and tapelibary to a VM? If yes, How?
I've tried my self, and read a lot of VMware forum posts. It seems like SAS isn't supported in ESXi 4.0 and forward, and due to connectivity problems from supporting multiple LUNs (both autoloader drive LUN and libary LUN) over the same HBA. You can run a commando i cli that enables the LUN that otherwise appears and offline, but the connection it self is still very unstable, and the connection to the autoloader fails whenever you want to run an operation?
Any guidance available out there, on how I solve this?
I've done a temp. setup with an extra setup, running a 3rd server with a SAS HBA and the backup software. Gbit ethernet and the SAS HBA directly connected to the autoloader. The problem here is very poor performance (220 mb / minut), since the data has to go from the VMs, over ethernet, and onto the backup server in order to get to the autoloader through SAS. Can this setup somehow be altered in order to increase the performance?
I have quotes for an autoloader + extended warranty and I am baffled by the high cost of the warranty uplift.
Why is the warranty cost high? Does it signal that autoloaders are a flawed solution?
I have an older HP NetServer LPr with what is apparently a Symbios SCSI card connecting to a Quantum SuperLoader 3 that is DLT based. From time to time, we seem to lose the connection to the autoloader. It's usually due to flaky power, but not totally sure why; sometimes when this happens the Autoloader's LED's are orange and it needs to be power cycled. The annoying workaround currently is to reboot the machine. As it is our production VPN and DNS server in addition to being our backup server, this is less than optimal.
In Debian (Sarge) is there not some command one can type to get the card to notice that it has the autoloader connected again?
dcr1:/proc# grep -i symbios /proc/pci
SCSI storage controller: LSI Logic / Symbios Logic 53c895 (rev 1).
dcr1:/proc# uname -a
Linux dcr1 2.4.27-3-686 #1 Tue Dec 5 21:03:54 UTC 2006 i686 GNU/Linux
dcr1:/proc# mt status
mt: /dev/tape: No such device
dcr1:/proc# ls -l /dev/tape
lrwxrwxrwx 1 root root 8 2007-02-07 16:01 /dev/tape -> /dev/st0
dcr1:/proc#
That mt status command will show the actual st0 status when things are working correctly. The No such device message is usually the second clue that we need to reboot - the first clue is usually that the backups didn't run.