04-16-2005
Seems like the easiest way to determine the capcity of the drives would be to look at the device itself, DDS? etc. All the device files for your tape drives will be located in /dev/rmt/*
Keith
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do I find if a server contains a DDS3 or a DDS2 drive remotely ?
I checked in SMIT and I noticed the description field according to tape drives, but is there another more thorough way?
Thanks,
Luke (0 Replies)
Discussion started by: Skywlkr235
0 Replies
2. BSD
Hello,
I have a little problem with backup & restoring files from tape drive.
I am adding 3 directories to my tape, and it is OK:
hades# tar -cvf /dev/nsa0 test test1 restore
a test
a test/level1
a test/myharddisk.img
a test1
a test1/level1
a test1/myharddisk.img
a test1/test.img
a... (1 Reply)
Discussion started by: d3m00n
1 Replies
3. AIX
Hi all,
Looking for an ls** command to display my tape drives and their associated serial numbers. thx. (8 Replies)
Discussion started by: jwholey
8 Replies
4. UNIX for Advanced & Expert Users
We have a new i500 and have 4 TLO4 drives which are connected directly to 2 FC cards on the host. The host can communicate with the autochanger through whichever drive that is set as control path.
When I run inquire, all 4 drives are listed but auto changer doesn't show up. Does anyone know... (1 Reply)
Discussion started by: tecky
1 Replies
5. Filesystems, Disks and Memory
Hi,
I am a abit new in AIX system administration field. I want to gather knowledge about backup techniques. As per my knowledge we use Tape archives for taking backups. Can anyone pls explain me in detail abt tape archive? Whether these tape archives come along with the systems or we have to... (1 Reply)
Discussion started by: forumsrahul
1 Replies
6. Solaris
I have a server/domain on a m5000 running Solaris 10. It is part of a cluster.
The other cluster member sees tape drives, but this one does not.
It is zoned correctly, and I can see the drives are binded in lputil.
The st.conf, and devlink.tab are identical.
ST.CONF: -
#
# Copyright... (1 Reply)
Discussion started by: pfwhufc
1 Replies
7. Solaris
hi,
i am using Solaris 8 on a sparc box and already have 4 tape drives in a backup libaray attached to my unix server. we have recently added 2 new tape drives to the libaray and now want to get unix to see them. have it working in windows.
how do i scan for new hardware and add theses new... (5 Replies)
Discussion started by: dshakey
5 Replies
8. Solaris
Hi,
I have a machine, and mpzio fails everytime i reboot the server. The machine has tape drives and SAN storage, I'm not sure if that is my issue or not. I was told to not enable mpxio globally as that would do something bad to the tape drives. So, I set it to only make the two SAN connected... (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
9. AIX
Good day!
Need help in checking my AIX 7.1 box.
After we have finished zoning our TS3200 and TS3310 tape libraries, we installed the Atape driver,
# lslpp -L |grep tape
Atape.driver 11.7.7.0 C F IBM AIX Enhanced Tape and
devices.fcp.tape.rte 7.1.3.15 C ... (0 Replies)
Discussion started by: alainken3
0 Replies
tz(4) Kernel Interfaces Manual tz(4)
Name
tz - SCSI magnetic tape interface
Syntax
VAX NCR 5380:
adapter uba0 at nexus?
controller scsi0 at uba0 csr 0x200c0080 vector szintr
tape tz0 at scsi0 drive 0
VAX DEC SII:
adapter ibus0 at nexus?
controller sii0 at ibus? vector sii_intr
tape tz0 at sii0 drive 0
RISC DEC SII:
adapter ibus0 at nexus?
controller sii0 at ibus? vector sii_intr
tape tz0 at sii0 drive 0
RISC DEC KZQ:
adapter uba0 at nexus?
controller kzq0 at ibus? csr 0761300vector sii_intr
tape tz0 at kzq0 drive 0
RISC NCR ASC:
adapter ibus0 at nexus?
controller asc0 at ibus? vector ascintr
tape tz0 at asc0 drive 0
Description
The SCSI tape driver provides a standard tape drive interface as described in This is a driver for any Digital SCSI tape device.
For the TZK10 QIC format tape drive, the densities supported are QIC-24 (read only) block size of 512 byte blocks, QIC-120, and QIC-150
read/write block size of 512 byte blocks, and QIC-320 read/write block size of 1024 byte blocks. With QIC format style tapes all reads and
writes must be in multiple of the block size. This is a requirement of fixed block tape drives because record boundaries are not pre-
served. The QIC densities are selected using the following special device names:
QIC-24 Fixed block size.
QIC-120 Fixed block size.
QIC-150 Fixed block size.
QIC-320 Fixed block size.
With all fixed block tape devices a of a file to the tape must be padded out. An example of this is a of which has a size of approximately
3800 bytes.
dd if=/etc/gettytab of=/dev/rmt0h bs=10k conv=sync
or
dd if=/etc/gettytab of=/dev/rmt0l bs=512 conv=sync
The option of pads the output to block size.
This driver also supports n-buffered reads and writes to the raw tape interface (used with streaming tape drives). See for further
details.
Tape Support
TZ30, TZK50, TLZ04, TSZ05, TKZ08, TZK10
Diagnostics
All diagnostic messages are sent to the error logger subsystem.
Files
See Also
mtio(4), nbuf(4), SCSI(4), MAKEDEV(8), uerf(8), tapex(8)
Guide to the Error Logger
tz(4)