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
vxvmconvert(1M) 														   vxvmconvert(1M)

NAME
vxvmconvert - convert LVM volume groups to VxVM disk groups SYNOPSIS
vxvmconvert DESCRIPTION
vxvmconvert is a menu-driven program to convert an HP Logical Volume Manger (LVM) configuration to a Veritas Volume Manager configuration. This man page is a brief overview of vxvmconvert. Refer to the Veritas Volume Manager Migration Guide for a detailed description before using the conversion procedure. The vxvmconvert script is interactive and prompts you for responses, supplying defaults where appropriate. There is a Help facility at every prompt. Enter a question mark (?) at a prompt to display a context-sensitive help message. With vxvmconvert you can identify LVM volume groups, list disks, analyze volume groups for conversion and complete the conversion of LVM volume groups to VxVM disk groups. LVM configurations are converted at the volume group level. All disks used in a volume group are converted together. You cannot use vxvm- convert to convert unused LVM disks (those not part of an LVM volume group) to VxVM disks. To convert unused LVM disks, use pvremove to take the disk out of LVM control, then initialize the disk for VxVM use by using vxdiskadm (see pvremove(1M) and vxdiskadm(1M) for more information). vxvmconvert changes disks within LVM volume groups to VxVM disks by replacing the areas of the disks used for LVM configuration information and with the equivalent VxVM volume configuration information. Portions of the disks used for user data, such as file systems and data- bases, are not affected by the conversion. The conversion process changes the names by which your system refers to the logical storage, so must be done offline. No applications can access data in the volume groups undergoing conversion. You must unmount file systems using those volumes and shut down any applications, such as databases, that might use the volumes directly. OPERATIONS
Analyze LVM Volume Groups for Conversion Use this operation to analyze one or more LVM volume groups for conversion to use by VxVM. The analysis checks for problems that can prevent the conversion from completing successfully. It calculates the space required to add volume group disks to a Volume Manager disk group. More than one volume group may be entered at the prompt. A grep-like pattern may be used to select multiple volume groups. See the ``Limitations in Conversion'' section in the Volume Manager Migration Guide for more information. Convert LVM Volume Groups to VxVM Converts one or more LVM volume groups to one or more VxVM disk groups. This adds the disks to a VxVM disk group and replaces existing LVM volumes with VxVM volumes. vxvmconvert prompts you to name the VxVM disk group that replaces the LVM volume group being converted. A default is suggested at the prompt. For example, if you are converting a volume group vg08, vxvmconvert renames it as dg08. See to the sections ``Dealing with New Logical Volume Names'' and ``Tailoring your VxVM Configuration'' in the Volume Manager Migration Guide for more information. Rollback from VxVM to LVM Rollback reverts VxVM disk groups to LVM volume groups. vxvmconvert provides a limited snapshot capability for the LVM metadata in a converted volume group. A snapshot is a simple protection method to use during conversion. Caution! Do not use this operation if the VxVM disk group was modified since the conversion. See to the section ``Restoring LVM Volume Groups and Disaster Recovery'' in the Volume Manager Migration Guide for more informa- tion. List Disk Information Displays information about the disks on a system. You can obtain detailed information about a disk by entering a specific disk device address. List LVM Volume Group Information Listvg displays a list of LVM volume groups. You can obtain detailed information about an LVM volume group at a specific disk device address. SEE ALSO
pvremove(1M), vgcfgbackup(1M), vgrestore(1M), vxdisk(1M), vxdiskadd(1M), vxdiskadm(1M), vxintro(1M) Veritas Volume Manager Migration Guide VxVM 5.0.31.1 24 Mar 2008 vxvmconvert(1M)
All times are GMT -4. The time now is 09:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy