Sponsored Content
Full Discussion: Is my XIV device open?
Operating Systems AIX Is my XIV device open? Post 303042984 by trifo75 on Wednesday 15th of January 2020 03:04:27 AM
Old 01-15-2020
zxmaus: thanks, but these commands are not what I meant. At least according to my findings.

Some of my systems have lots of LUN-s, used for various purposes:
* used as PV-s in some VG-s (mostly rootvg)
* used as GPFS NSD backing devices
* used as Oracle ASM data disks
and some more.

Your commands can show relevant info only for LUNS used as PV disks, but they are misleading on other cases.

Now I can try to run
Code:
rmdev -l hdiskXX

and see if it can put the device into DEFINED state. When the device is open, I get an error and the device state is kept unchanged. But I would like to find a way to obtain the same info without modifying the system. By the way, how does rmdev find this info?

--Trifo
 

9 More Discussions You Might Find Interesting

1. Solaris

ERROR: Can't open boot-device

Hi i need help pls ... Server type sun fire 3800 I need to install solaris 9 . When i boot the system i recieve the following : System Controller 'sunfire3800': Type 0 for Platform Shell Type 1 for domain A console Type 2 for domain B console Type 3 for... (5 Replies)
Discussion started by: tt155
5 Replies

2. Solaris

Can't open boot device

I have a real emergency. I have a Sun Fire V240 UltraSparc server and am connected via the Serial Mgmnt Port with a Laptop. I have been building an Oracle database on it for the past couple months, not getting very far along with it , when suddenly, the system had a fatal crash. I've lost the... (2 Replies)
Discussion started by: mayewil
2 Replies

3. Solaris

"Can't open boot device" error !!

I've a Sun V440 machine, and it's running solaris 10 .. for some reason i need to install a fresh copy of solaris 10. for that i've prepared solaris 10 dvd but surprisingly i found there is no any dvd rom on this machine, so i've took a dvd rom from a V240 machine and inserted on V440. after... (3 Replies)
Discussion started by: Anti_Evil
3 Replies

4. Solaris

Solaris with Soft Errors in XIV

Hi guys, I had a solaris box, with veritas controled disk. 1 disc is showing soft errors, how can I repair the soft errors? Please help. Cheers; (4 Replies)
Discussion started by: Mujakol
4 Replies

5. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

6. AIX

Unable to varyonvg after copy vg from XIV

Hi all, I am not sure whether anyone of you using XIV to copy vg from one host to another. After I managed to copy all the respective vg over to destination vg, and map all vg to destination and when come to varyonvg, I got the following error 0516-510 varyonvg: Physical volume not found for... (2 Replies)
Discussion started by: ckwan
2 Replies

7. Solaris

Can't open boot device

I installed a new hard drive completely blank. sun blade 150 openboot 4.10.6 message: Boot device: disk:a File and args: Bad magic number in disk label Can't open label package Evaluating: Can't open boot device (15 Replies)
Discussion started by: janiper
15 Replies

8. Solaris

Can't open boot device..

Hello Forum, I'm really in a fix now, I'm getting this error message now, seems like the boot block is damaged? When I do probe-all the system freezes... Can any one guide me as what to do next? System is Solaris 8 running Open Boot PROM 4 System also does not have a cd/dvd rom drive... ... (17 Replies)
Discussion started by: br1an
17 Replies

9. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

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
CD(9)							   BSD Kernel Developer's Manual						     CD(9)

NAME
cd -- CDROM driver for the CAM SCSI subsystem DESCRIPTION
The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type com- mands. Some drives do not behave as the driver expects. See the QUIRKS section for information on possible flags. QUIRKS
Each CD-ROM device can have different interpretations of the SCSI spec. This can lead to drives requiring special handling in the driver. The following is a list of quirks that the driver recognize. CD_Q_NO_TOUCH This flag tell the driver not to probe the drive at attach time to see if there is a disk in the drive and find out what size it is. This flag is currently unimplemented in the CAM cd driver. CD_Q_BCD_TRACKS This flag is for broken drives that return the track numbers in packed BCD instead of straight decimal. If the drive seems to skip tracks (tracks 10-15 are skipped) then you have a drive that is in need of this flag. CD_Q_NO_CHANGER This flag tells the driver that the device in question is not a changer. This is only necessary for a CDROM device with multiple luns that are not a part of a changer. CD_Q_CHANGER This flag tells the driver that the given device is a multi-lun changer. In general, the driver will figure this out auto- matically when it sees a LUN greater than 0. Setting this flag only has the effect of telling the driver to run the initial read capacity command for LUN 0 of the changer through the changer scheduling code. CD_Q_10_BYTE_ONLY This flag tells the driver that the given device only accepts 10 byte MODE SENSE/MODE SELECT commands. In general these types of quirks should not be added to the cd(4) driver. The reason is that the driver does several things to attempt to determine whether the drive in question needs 10 byte commands. First, it issues a CAM Path Inquiry command to determine whether the protocol that the drive speaks typically only allows 10 byte commands. (ATAPI and USB are two prominent exam- ples of protocols where you generally only want to send 10 byte commands.) Then, if it gets an ILLEGAL REQUEST error back from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10 byte version of the command instead. The only reason you would need a quirk is if your drive uses a protocol (e.g., SCSI) that typically does not have a problem with 6 byte commands. FILES
/sys/cam/scsi/scsi_cd.c is the driver source file. SEE ALSO
cd(4), scsi(4) HISTORY
The cd manual page first appeared in FreeBSD 2.2. AUTHORS
This manual page was written by John-Mark Gurney <gurney_j@efn.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry <ken@FreeBSD.org>. BSD
September 2, 2003 BSD
All times are GMT -4. The time now is 08:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy