Tape library

[Tony Alfrey]

Net Llama! wrote:
> On Wed, 6 Jun 2007, Dirk Moolman wrote:
>> I have a Neo tape library connected to one of my Linux servers (SLES 9)
>>
>> One of my collegues tell me that the device names are /dev/obt0, and
>> /dev/obt1.
>> There are tapes loaded in both drives, but I cannot write to them using
>> these devices.
>>
>> tar cvf /dev/obt0 *
>> tar: /dev/obt0: Cannot open: No such device or address
>> tar: Error is not recoverable: exiting now
> 
> One of your collegues is an idiot.  I've never heard of any Linux kernel 
> setting /dev/obt as a block device for anything. 
> /usr/src/linux/Documentation/devices.txt defines all the devices known to 
> the kernel.
> 

See 
http://download-east.oracle.com/docs/cd/B19306_01/install.102/b14235/obins_int.htm


"On Linux or Solaris, the resulting device special file names for tape 
libraries are /dev/obl1, /dev/obl2, /dev/obl3 and so on, and the names 
for tape drives are /dev/obt1, /dev/obt2, /dev/obt3 and so on through 
/dev/obtn, where n in each case is the Oracle Secure Backup logical unit 
number you assigned the device. On Windows, the resulting tape library 
names are obl1, obl2, obl3 and so on, and the names for tape drives are 
obt1, obt2, obt3 and so on, where these names are assigned automatically 
during the installation of Oracle Secure Backup on Windows. (Note that 
the l character in the name of each tape drive is a lower-case L, not a 
numeral 1.)"

Perhaps his experience is guided by past Oracle usage?


-- 
Tony Alfrey
tonyalfrey at earthlink.net
"I'd Rather Be Sailing"