12-08-2009
Here is the output of the lsdev
# lsdev -Cc tape
rmt0 Available 09-08-00-0,0 LVD SCSI 4mm Tape Drive
#
10 More Discussions You Might Find Interesting
1. Linux
Hi,
Will someone help in giving the clue to installating Travan Tape drive on Redhat 8.0
Kayode (1 Reply)
Discussion started by: kayode
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
I' using a sun solaris server, I would like to known if there is the possibility to control how many space is free on a tape and how I can delete a single file on a tape.
Thanks
DOMENICO (3 Replies)
Discussion started by: Minguccio75
3 Replies
3. SCO
when I do a tape status /dev/rStp0 I get the following on a new tape and I have tried several:
Status : ready beginning-of-tape
soft errors : 0
hard errors: 2
underruns: 5
My BackupEdge has stopped backing up my system because it asks for a new volume yet my total system data is under 20... (5 Replies)
Discussion started by: psytropic
5 Replies
4. Solaris
Well I have just added new tape drive to my server (lto)
However I am getting few errors in using it. I have checked status with
#iostat -En : giving me few hard errors, few soft errors and execution error.
Also tape status is not visible as "no sense" its coming as "no additional sense".
I... (5 Replies)
Discussion started by: saurabh84g
5 Replies
5. Solaris
Hi all,
I have solaris 10 sparc running and working very well
but i have problem with external SCSI tape drive DAT 72 problem
it seems to me the tape drive is manufactured by SUN microsystems
when i ran ls -l /dev/rmt/0
it reveals the following output
bash-3.00# mt -f /dev/rmt/0... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
6. Red Hat
I'm using tar and so far so good, but how can I view ALL files without having to fast forward and rewind the tape? Let's say I append 100 files onto the tape. Having to fast forward 100 times until I find the file I want is kinda tedious. (3 Replies)
Discussion started by: sdotsen
3 Replies
7. SCO
Looking for specifically naming convention for a tape device for SCO Unix
What full system backup command should I use for SCO UNIX (1 Reply)
Discussion started by: jedimaster
1 Replies
8. Solaris
hi, was wondering if there is a problem with the patches, and if we wish to restore everything back to square one, how should we go about using ufsrestore from a DAT tape of ufsdump backup data ? (1 Reply)
Discussion started by: Exposure
1 Replies
9. UNIX for Dummies Questions & Answers
We have a SCO UnixWare system version 7.1.3, running a front end ERP system on a Compaq/HP Proliant ML370 server.
Compaq ProLiant ML370 Server
I change the tape everyday to do a daily back up. When I pressed the eject button last night it failed to spit the tape out.....HELP.
1) Is this... (12 Replies)
Discussion started by: Mick_Dundee
12 Replies
10. Shell Programming and Scripting
How to use 'ls' command to list files like *.dat, not *.*.dat (5 Replies)
Discussion started by: pmcginni777
5 Replies
LSDEV(8) Linux System Manual LSDEV(8)
NAME
lsdev - display information about installed hardware
SYNOPSIS
lsdev
DESCRIPTION
lsdev gathers information about your computer's installed hardware from the interrupts, ioports and dma files in the /proc directory, thus
giving you a quick overview of which hardware uses what I/O addresses and what IRQ and DMA channels.
OPTIONS
None.
FILES
/proc/interrupts
IRQ channels.
/proc/ioports
I/O memory addresses.
/proc/dma
DMA channels.
BUGS
lsdev can't always figure out which lines in the three examined files refer to one and the same device, because these files sometimes use
different names for the same piece of hardware. For example, in some kernels the keyboard is referred to as `kbd' in /proc/ioports and as
`keyboard' in /proc/interrupts. This should be fixed in the kernel, not in lsdev (as has indeed happened for this particular example).
The program does however try to match lines by stripping anything after a space or open parenthesis from the name, so that e.g. the
`serial' lines from /proc/interrupts match the `serial(set)' lines from /proc/ioports. This attempt at DWIM might be considered a bug in
itself.
This program only shows the kernel's idea of what hardware is present, not what's actually physically available.
SEE ALSO
procinfo(8).
AUTHOR
Sander van Malssen <svm@kozmix.cistron.nl>
3rd Release 1998-05-31 LSDEV(8)