Sponsored Content
Full Discussion: Tape drive defined
Operating Systems AIX Tape drive defined Post 302371096 by lo-lp-kl on Friday 13th of November 2009 10:42:06 AM
Old 11-13-2009
Tape drive defined

Thanks for your reply zxmaus

I have 5 drives physically.

one 4mm and 4 drives (library model 3583)


Thanks again for the comments
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Tape drive install

I'm trying to install a tape drive on a compaq SCO OS 505. well I have gone through the mkdev tape comands and what have you yet no luck. when I reboot and do a simple tape rewind it gives me an error no such device etc.etc. IS there a diference in the xct0 and rct0 a the default? help.. (2 Replies)
Discussion started by: kikkin
2 Replies

2. AIX

4MM Tape Drive

Hello all, I have just installed an HP dat72 external tape drive to an IBM 275 Intellistation (AIX 5L). It was installed as an Other SCSI Tape Drive (rmt1). I am using the Web Based System Manager at this point to do an initial backup of a journaled file system. I am getting an error and am... (1 Reply)
Discussion started by: joeweisser
1 Replies

3. UNIX for Dummies Questions & Answers

tape drive

Hi, I need to restore my tape backup, when I type "tape status" it gives; status : ready beginning-of-tape write-protected soft errors : 0 hard errors : 0 underruns : 3 but... (4 Replies)
Discussion started by: alisevA3
4 Replies

4. SCO

Restore from HP Tape Drive

Here is the scenario. We have an billing system that ran on SCO 5.0.6. The HP Netserver went dwon, along with SCSI disks. They are unretrievable. I installed an IDE HDD, and reinstalled SCO. I am not too familiar w/ SCO or UNIX, and need to know how to install Tape drive, and how to restore from... (11 Replies)
Discussion started by: jlewis808
11 Replies

5. AIX

Tape Drive

I have tape drive in one Lpar. when i saw that time tape is in defined state. After that i deleted the tape drive using the rmdev -R command. Then fired the cfgmgr -v command. But I am not getting the tape drive. Now the drive is even not in defined state also. It is not shown the tape drive. How... (1 Reply)
Discussion started by: pernasivam
1 Replies

6. Solaris

Tape drive problems

Recently we had a problem with a CPU card on our SunFire V880 which has Solaris 9 OS. we removed the card and there was also a problem with our usr which was accidentally deleted. We able to restore the usr but now we having a problem with our tape drive. Previously we could write to the with ... (5 Replies)
Discussion started by: rahmantanko
5 Replies

7. Solaris

Help with tape drive

Hey folks, Linux admin here, forced to use Opensolaris to try to use ufsdump/ufsrestore to get some data of some old tapes. I've got Opensolaris 2009.06 on x86 and a Sony SDX-700V. As a "control" experiment, I booted the system with a Linux live CD and the tape drive worked perfectly. ... (2 Replies)
Discussion started by: eddy_sysad
2 Replies

8. HP-UX

TAPE drive

I have used ioscan -fnC tape and the system identified the tape drive. what is the command to show a listing of what is on the tape? I have used ls /dev/rmt/rmt0 to no avail. can anyone help? Thanks in advance (10 Replies)
Discussion started by: Randydog
10 Replies
VMSTAT(1)						      General Commands Manual							 VMSTAT(1)

NAME
vmstat - report virtual memory statistics SYNOPSIS
vmstat [ -fsi ] [ drives ] [ interval [ count ] ] DESCRIPTION
Vmstat delves into the system and normally reports certain statistics kept about process, virtual memory, disk, trap and cpu activity. If given a -f argument, it instead reports on the number of forks and vforks since system startup and the number of pages of virtual memory involved in each kind of fork. If given a -s argument, it instead prints the contents of the sum structure, giving the total number of several kinds of paging related events which have occurred since boot. If given a -i argument, it instead reports on the number of inter- rupts taken by each device since system startup. If none of these options are given, vmstat will report in the first line a summary of the virtual memory activity since the system has been booted. If interval is specified, then successive lines are summaries over the last interval seconds. ``vmstat 5'' will print what the system is doing every five seconds; this is a good choice of printing interval since this is how often some of the statistics are sampled in the system; others vary every second, running the output for a while will make it apparent which are recomputed every second. If a count is given, the statistics are repeated count times. The format fields are: Procs: information about numbers of processes in various states. r in run queue b blocked for resources (i/o, paging, etc.) w runnable or short sleeper (< 20 secs) but swapped Memory: information about the usage of virtual and real memory. Virtual pages are considered active if they belong to processes which are running or have run in the last 20 seconds. A ``page'' here is 1024 bytes. avm active virtual pages fre size of the free list Page: information about page faults and paging activity. These are averaged each five seconds, and given in units per second. re page reclaims (simulating reference bits) at pages attached (found in free list) pi pages paged in po pages paged out fr pages freed per second de anticipated short term memory shortfall sr pages scanned by clock algorithm, per-second up/hp/rk/ra: Disk operations per second (this field is system dependent). Typically paging will be split across several of the available drives. The number under each of these is the unit number. Faults: trap/interrupt rate averages per second over last 5 seconds. in (non clock) device interrupts per second sy system calls per second cs cpu context switch rate (switches/sec) Cpu: breakdown of percentage usage of CPU time us user time for normal and low priority processes sy system time id cpu idle If more than 4 disk drives are configured in the system, vmstat displays only the first 4 drives, with priority given to Massbus disk drives (i.e. if both Unibus and Massbus drives are present and the total number of drives exceeds 4, then some number of Unibus drives will not be displayed in favor of the Massbus drives). To force vmstat to display specific drives, their names may be supplied on the command line. FILES
/dev/kmem, /vmunix SEE ALSO
systat(1), iostat(1) The sections starting with ``Interpreting system activity'' in Installing and Operating 4.2bsd. 4th Berkeley Distribution March 15, 1986 VMSTAT(1)
All times are GMT -4. The time now is 07:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy