Sponsored Content
Full Discussion: Is my XIV device open?
Operating Systems AIX Is my XIV device open? Post 303043059 by zxmaus on Friday 17th of January 2020 01:31:46 AM
Old 01-17-2020
yes you are correct - that is why I asked yesterday what you meant with open - for both disks you get output - so the disks are open - so correctly zoned and readable/writable.

As stated before, as you have this strange mix of different types of disks, you will have to determine the hard way which ones you are using. I am guessing the asm disks have been defined by you via mknod command so you should be able via major/minor number to determine which those are - but I don't think you can find out if they are used or not without asking your DBAs what they have configured.
This User Gave Thanks to zxmaus For This Post:
 

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
TARG(4) 						   BSD Kernel Interfaces Manual 						   TARG(4)

NAME
targ -- SCSI target emulator driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device targ DESCRIPTION
The targ driver provides an interface for usermode programs to emulate SCSI target devices. A sample program that emulates a disk drive (similar to da(4)) can be found in /usr/share/examples/scsi_target. The targ driver supplies the control device /dev/targ. After opening the device, the file descriptor must be bound to a specific bus/tar- get/LUN and enabled to process CCBs using the TARGIOCENABLE ioctl. The process then uses write(2) to send CCBs to the SIM and poll(2) or kqueue(2) to see if responses are ready. Pointers to completed CCBs are returned via read(2). Any data transfers requested by the user CCBs are done via zero-copy IO. IOCTLS
The following ioctl(2) calls are defined in the header file <cam/scsi/scsi_targetio.h>. TARGIOCENABLE (struct ioc_enable_lun) Enable target mode on the LUN specified by the following structure: struct ioc_enable_lun { path_id_t path_id; target_id_t target_id; lun_id_t lun_id; int grp6_len; int grp7_len; }; The selected path (bus), target, and LUN must not already be in use or EADDRINUSE is returned. If grp6_len or grp7_len are non-zero, reception of vendor-specific commands is enabled. TARGIOCDISABLE Disable target mode and abort all pending CCBs. The CCBs may optionally be read as they complete. TARGIOCENABLE can then be called to activate a different LUN. Multiple disable calls have no effect. The close(2) system call automatically disables target mode if enabled. TARGIOCDEBUG (int) Enables CAM_PERIPH debugging if the argument is non-zero, otherwise disables it. FILES
<cam/scsi/scsi_targetio.h> describes the usermode interface. /sys/cam/scsi/scsi_target.c is the driver source file. /dev/targ is the control device. SEE ALSO
/usr/share/examples/scsi_target, ahc(4), isp(4), scsi(4) FreeBSD Target Information, http://www.root.org/~nate/freebsd/. AUTHORS
The targ driver first appeared in FreeBSD 3.0 and was written by Justin T. Gibbs. It was rewritten for FreeBSD 5.0 by Nate Lawson <nate@root.org>. BUGS
Currently, only the ahc(4) and isp(4) drivers fully support target mode. The ahc(4) driver does not support tagged queuing in target mode. BSD
December 13, 2011 BSD
All times are GMT -4. The time now is 02:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy