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

NAME
vxconfigrestore - restore disk group configuration SYNOPSIS
/etc/vx/bin/vxconfigrestore [-c | -d | -n | -p] [-l directory] {dgname | dgid} DESCRIPTION
The vxconfigrestore utility is used to restore a disk group's configuration information if this has been lost or become corrupted. The disk group whose configuration is to be restore is specified either by name or by ID. Any disks whose private region headers have become corrupted are reinstalled when the disk group configuration is restored. If you choose not to reinstall the VxVM headers for these disks, it may not be possible to restore the disk group. The disk group configuration backup files may have been automatically created by the vxconfigbackupd daemon, or manually by running the vxconfigbackup command. Restoration of a disk group configuration has two stages: precommit and commit. The precommit stage allows you to temporarily load the con- figuration that is to be restored, and examine it using the vxprint utility. At this stage, the disk group configuration is read-only. No permanent changes are written to disk until you choose to commit them. If desired, you can abandon the restore operation at the precommit stage. OPTIONS
-c (Commit) Permanently commits changes to the disks. The restoration must be at the precommit stage for this command to succeed. Volumes are synchronized in the background. For large volume configurations, it may take some time to perform the synchroniza- tion. You can use the vxtask -l list command to monitor the progress of this operation. -d (Decommit) Abandons the restore operation at the precommit stage. -n (Precommit: no installation of VxVM disk header) Loads the disk group configuration at the precommit stage. This option speci- fies that disks whose private region headers have become corrupted are not to be reinstalled. -l directory Specifies a directory other than the default (/etc/vx/cbr/bk) where the backup configuration files are located. -p (Precommit: load) Loads the disk group configuration at the precommit stage. This option specifies that disks whose private region headers have become corrupted are to be reinstalled. The vxprint command can be used to examine the disk group configura- tion. Note: The volumes have not yet been synchronized at this stage. This is the default operation if no option is specified. EXAMPLES
Load the configuration of the mydg disk group from the default directory, and reinstall disks that have corrupted VxVM disk headers: vxconfigrestore -p mydg Load the configuration of the mydg1 disk group from the backup files in the directory /dgbackup/mydg1 without reinstalling any disks that have corrupted private region disk headers: vxconfigrestore -n -l /dgbackup/mydg1 mydg1 Abandon the restoration of the mydg2 disk group at the precommit stage: vxconfigrestore -d -l /dgbackup/mydg2 mydg2 Commit the restoration of the configuration of the mydg disk group from the backup files in the directory /dgbackup/mydg: vxconfigrestore -c -l /dgbackup/mydg mydg FILES
/etc/vx/cbr/bk/dgname.dgid/dgid.dginfo Default location of backup file for disk group information. /etc/vx/cbr/bk/dgname.dgid/dgid.diskinfo Default location of backup file for disk attributes. /etc/vx/cbr/bk/dgname.dgid/dgid.binconfig Default location of backup file for binary configuration copy. /etc/vx/cbr/bk/dgname.dgid/dgid.cfgrec Default location of backup file for configuration records in vxprint -m format. NOTES
A disk group must be restored on the same physical disks as are defined in the configuration backup files. The disk group configuration backup and restore utilities do not save any data in the public region. This includes file system or other application data that is configured within VxVM objects. A shared disk group in a cluster is restored as a private disk group. After the commit phase has completed, you can deport the private disk group and re-import it as a shared disk group. SEE ALSO
vxconfigbackup(1M), vxconfigbackupd(1M) VxVM 5.0.31.1 24 Mar 2008 vxconfigrestore(1M)
All times are GMT -4. The time now is 01:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy