Sponsored Content
Full Discussion: Tape Drive
Operating Systems AIX Tape Drive Post 302237475 by bakunin on Wednesday 17th of September 2008 05:41:28 PM
Old 09-17-2008
Only devices in state "Available" are usable. A device in state "Defined" means that once there was such a device but has been removed/inactivated since and only the devices information is still left.

Exactlxy this definition you have removed by issuing rmdev. (Btw. consider using the "-d" switch to rmdev.) When you ran cfgmgr again the device was not created because it has still not been there and therefor the config manager had no reason to create the device entries (in the ODM). But the device was not attached to the machine (or simply switched off) before either because otherwise the devices status wouldn't have been "Defined".

To answer your question: you can immediately tell that the device is unusable, because if it would be usable it would at least be in state "Available".

I hope this helps.

bakunin
 

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. Linux

Installing tape drive?

Hello. I have Redhat 8.0 on a laptop. Working good. I wanted to install the tape drive that is physically attached to it. The tape drive worked fine under Windows98SE. It's one of those parallel QIC-80 drives and I confirmed that it is supported by FTape. It appears that FTape might already... (0 Replies)
Discussion started by: RuralTurtle
0 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

Tape Drive Configuration

Dear All, I have a tape drive which has worked for offer 3yrs properly on SCO Openserver Release = 3.2v5.0.5. I tried to clean it all invain. I did a fresh installation of unix of the same OS and did the configuration still didn't bear fruits. The tape is a scsi and the configuration is as... (4 Replies)
Discussion started by: njoroge
4 Replies

5. 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

6. SCO

Tape Drive Logs?

I've recently been tasked with "refurbishing" an HP Proliant ML370 running SCO 5.0...something. This is primarily used for legacy support and is kept on a shelf for safe keeping. The scope of work includes hardware diagnostics and blowing the dust out. I have run HP diagnostics on the array,... (1 Reply)
Discussion started by: v1corp
1 Replies

7. UNIX for Dummies Questions & Answers

Quantum tape drive

Hi, Using Redhat 5.7. I have Quantum tape drive connected to the server. I am trying to install the Netbackup software. Just wondering how can I see the Quantum is connected to the server. is any command I run to see the tape drive is connected? I used to work on Solaris, I used to do... (1 Reply)
Discussion started by: samnyc
1 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
devfs(7FS)                                                         File Systems                                                         devfs(7FS)

NAME
devfs - Devices file system DESCRIPTION
The devfs filesystem manages a name space of all devices under the Solaris operating environment and is mounted during boot on the /devices name space. The /devices name space is dynamic and reflects the current state of accessible devices under the Solaris operating environment. The names of all attached device instances are present under /devices. The content under /devices is under the exclusive control of the devfs filesystem and cannot be changed. The system may be configured to include a device in one of two ways: By means of dynamic reconfiguration (DR), using, for example, cfgadm(1M). For devices driven by driver.conf(4) enumeration, edit the driver.conf file to add a new entry, then use update_drv(1M) to cause the system to re-read the driver.conf file and thereby enumerate the instance. The device may be attached through a number of system calls and programs, including open(2), stat(2) and ls(1). During device attach, the device driver typically creates minor nodes corresponding to the device via ddi_create_minor_node(9F). If the attach is successful, one or more minor nodes referring to the device are created under /devices. Operations like mknod(2), mkdir(2) and creat(2) are not supported in /devices. FILES
/devices Mount point for devfs file system SEE ALSO
devfsadm(1M), vfstab(4), attach(9E) NOTES
The /devices name space cannot be unmounted. All content at or below the /devices name space is an implementation artifact and subject to incompatible change or removal without notifi- cation. SunOS 5.10 26 Oct 2004 devfs(7FS)
All times are GMT -4. The time now is 06:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy