Sponsored Content
Full Discussion: Is my XIV device open?
Operating Systems AIX Is my XIV device open? Post 303043009 by zxmaus on Wednesday 15th of January 2020 08:24:31 PM
Old 01-15-2020
if you do this on ASM disks or gpfs disks you are wiping the header. The device will stay up til your next reboot and be beautiful and clean after the reboot so this is a terrible idea.

You do get an output from the commands I listed even with ASM devices and GPFS disks and even from completely unassigned open disks. It might be a cryptic unreadable output but it is an output. If you get nothing or a one-line-error the disks are not open.

But maybe I have a different understanding what open means. Are you trying to find out if the disks are unused? Are you using AIX mpio or any kind of multipathing software? With ASM, before you make ANY changes to the disks, ask the DBAs to backup the disk headers. Strictly speaking by design, AIX has no idea if the disks are used or not - but oracle will hold a lock on them while still allocated - which is a curse and a blessing for above reason - you will STILL wipe the header. For gpfs, the cluster itself should be able to tell you which disks it is using - try
Code:
mmlsnsd

command. For normal disks in VGs, a simple
Code:
lspv

will tell you which disks are not in use from LVM perspective.

Last edited by zxmaus; 01-15-2020 at 09:31 PM..
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
format(1M)																format(1M)

NAME
format - format an HP SCSI disk array LUN SYNOPSIS
device_file DESCRIPTION
formats one LUN of the HP SCSI disk array associated with device file, device_file. The format will usually be a soft or zeroing format, in which the controller writes zeroes to the data area and parity area, if any, of the LUN. NOTE: The above should always be true of a sub-LUN, but the controller might decide, based on certain conditions, to do a full format of a regular LUN, which consists of sending a mode select and a media initialization command to the physical drive(s) in question, fol- lowed by zeroing the data and parity area, if any. The conditions which will cause a full format to be done are as follows: 1. The controller received a Mode Select command which requires a drive sector size change. 2. The controller received a Mode Select command which changed a parameter in the Format Device Page(0x03). 3. The LUN contains one or more failed drives. In this case only a certain subset of the drives containing the failed drives will be formatted. 4. Either the FmtData or the CmpLst bit in the Format Unit CDB is set. RETURN VALUE
returns the following values: 0 Successful completion. -1 Command failed. DIAGNOSTICS AND ERRORS
Errors can originate from problems with: o o SCSI (device level) communications o system calls Error messages generated by format: An error in command syntax has occurred. Enter command again with all required arguments, in the order shown. To ensure that does not modify a disk array that is being used by another process, attempts to obtain exclusive access to the disk array. If the disk array is already opened by another process (for example, LVM -- the Logical Volume Manager), a "" error message is returned by the driver. To eliminate the "" condition, determine what process has the device open. In the case of LVM, it is necessary to deactivate the volume group containing the array before formatting array LUNs (see vgchange(1M)). The LUN number, which is derived from the device file name, is out of range. The addressed LUN is not configured, and thus is not known to the array controller. Utilities must be able to open the device file for raw access. The device being addressed is not an HP SCSI disk array. SCSI (device level) communication errors: Sense data associated with the failed operation is printed. Error messages generated by system calls: uses the following system calls: and Documentation for these HP-UX system calls contains information about the specific error conditions associated with each call. does not alter the value of The interpretation of for printing purposes is performed by the system utility EXAMPLES
To format the HP SCSI disk array LUN on a Series 800: WARNING
The command will destroy all user data on the addressed LUN. DEPENDENCIES
The HP C2425 and HP C2427 disk arrays are only supported on Series 700 systems running HP-UX version 9.0X. The HP C2430 disk array is supported on Series 700 and 800 systems running HP-UX versions 9.0X and 10.0X. AUTHOR
was developed by HP. format(1M)
All times are GMT -4. The time now is 09:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy