10 More Discussions You Might Find Interesting
1. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
2. AIX
Hi all
The situation is as follows:
We need to take an mksysb image from an AIX 6.1 server. From some reason (irrelevant to this discussion) this server does not have access to a local CD-ROM or a tape drive. We do have another server with AIX 6.1 (but different technology level) which got access... (1 Reply)
Discussion started by: abohmeed
1 Replies
3. AIX
Hi All,
After (by accident) closing a session that ran a restore command I can not access the tape drive anymore.
I get the following error:
# tctl -f /dev/rmt0 rewind
/dev/rmt0: Resource temporarily unavailable
But I cannot find any processes associated with the tape device:
# ps... (2 Replies)
Discussion started by: petervg
2 Replies
4. Solaris
After we upgraded one PW450 machine from (networker 7.2 & solaris 9) to (networker 7.4 and solaris 10) through scratch installation
Only one of two HP tape drives is shown in inquire command
And we are getting strange logs in messages file (attached)
For 2nd drive 1cbn character specific file... (4 Replies)
Discussion started by: kashif_islam
4 Replies
5. UNIX for Dummies Questions & Answers
I disconected external device which was configured as rmt0. When I connect it again and run cfgmgr device name has changed (internal drive which was rmt1 is now rmt0 and external drive was rmt0 and is rmt1) and I dont know how to back it out. The thing is that for all backups I use new modell... (2 Replies)
Discussion started by: fraydey
2 Replies
6. Solaris
Hi to all,
I´m recovering a Solaris box trough jumpstart with restore of a flash archive on tape. The tape device is recognized by OBP in probe-scsi-all and by the operating system that is instaled on that box where i want to restore flar as /dev/rmt/2. But when a i boot with " (0) ok boot net -... (0 Replies)
Discussion started by: spacewalker
0 Replies
7. Solaris
Hi,
Someone knows hot to create a flash archive to a remote tape device?
Here is my try:
$flarcreate -n nereus -S -t lisdev:/dev/rmt/1n
WARNING: hash generation disabled when using tape (-t)
current filter settings
Creating the archive...
ERROR: Unable to work archive.
Regards (4 Replies)
Discussion started by: spacewalker
4 Replies
8. UNIX for Dummies Questions & Answers
Eh... what the title says. :) (8 Replies)
Discussion started by: PSC
8 Replies
9. SCO
i have a sco-unix box. I want to access tape driver (sdt-700) on scsi. but i dont know how? where is this device file for tape driver is located? how do i access this tape? pls help this fool. (1 Reply)
Discussion started by: mchitrakar
1 Replies
10. Programming
Hi,
I have problem detecting my tape drive.
In SAM, once I click on the either Automated Backups or Interactive Backup and Recovery icon, the screen will prompt searching for device and ..... nothing appears in the list.
In the end, I have the kill the SAM process and reboot the system and... (1 Reply)
Discussion started by: jennifer
1 Replies
MTIO(4) BSD Kernel Interfaces Manual MTIO(4)
NAME
mtio -- generic magnetic tape I/O interface
SYNOPSIS
#include <sys/ioctl.h>
#include <sys/types.h>
#include <sys/mtio.h>
DESCRIPTION
Magnetic tape has been the computer system backup and data transfer medium of choice for decades, because it has historically been cheaper in
cost per bit stored, and the formats have been designed for portability and storage. However, tape drives have generally been the slowest
mass storage devices attached to any computer system.
Magnetic tape comes in a wide variety of formats, from classic 9-track, through various Quarter Inch Cartridge (QIC) variants, to more modern
systems using 8mm video tape, and Digital Audio Tape (DAT). There have also been a variety of proprietary tape systems, including DECtape,
and IBM 3480.
UNIX TAPE I/O
Regardless of the specific characteristics of the particular tape transport mechanism (tape drive), UNIX tape I/O has two interfaces: "block"
and "raw". I/O through the block interface of a tape device is similar to I/O through the block special device for a disk driver: the indi-
vidual read(2) and write(2) calls can be done in any amount of bytes, but all data is buffered through the system buffer cache, and I/O to
the device is done in 1024 byte sized blocks. This limitation is sufficiently restrictive that the block interface to tape devices is rarely
used.
The "raw" interface differs in that all I/O can be done in arbitrary sized blocks, within the limitations for the specific device and device
driver, and all I/O is synchronous. This is the most flexible interface, but since there is very little that is handled automatically by the
kernel, user programs must implement specific magnetic tape handling routines, which puts the onus of correctness on the application program-
mer.
DEVICE NAME CONVENTIONS
Each magnetic tape subsystem has a couple of special devices associated with it.
The block device is usually named for the driver, e.g. /dev/st0 for unit zero of a st(4) SCSI tape drive.
The raw device name is the block device name with an "r" prepended, e.g. /dev/rst0.
By default, the tape driver will rewind the tape drive when the device is closed. To make it possible for multiple program invocations to
sequentially write multiple files on the same tape, a "no rewind on close" device is provided, denoted by the letter "n" prepended to the
name of the device, e.g. /dev/nst0, /dev/nrst0.
The mt(1) command can be used to explicitly rewind, or otherwise position a tape at a particular point with the no-rewind device.
FILE MARK HANDLING
Two end-of-file (EOF) markers mark the end of a tape (EOT), and one end-of-file marker marks the end of a tape file.
By default, the tape driver will write two End Of File (EOF) marks and rewind the tape when the device is closed after the last write.
If the tape is not to be rewound it is positioned with the head in between the two tape marks, where the next write will over write the sec-
ond end-of-file marker.
All of the magnetic tape devices may be manipulated with the mt(1) command.
A number of ioctl(2) operations are available on raw magnetic tape. Please see <sys/mtio.h> for their definitions.
The manual pages for specific tape device drivers should list their particular capabilities and limitations.
SEE ALSO
dd(1), mt(1), pax(1), tar(1), st(4), wt(4)
HISTORY
The mtio manual appeared in 4.2BSD.
BUGS
The status should be returned in a device independent format.
If and when NetBSD is updated to deal with non-512 byte per sector disk media through the system buffer cache, perhaps a more sane tape
interface can be implemented.
BSD
January 14, 1999 BSD