flags online error private autoconfig North Grosvenordale Connecticut

Business or Home Computer Service

Address 4 Clockedile Dr, Oxford, MA 01540
Phone (888) 694-8669
Website Link
Hours

flags online error private autoconfig North Grosvenordale, Connecticut

by running vxdctl enable), then VxVM will in turn mark the disk with error "Disk is not usable".  (DMP will not log further messages in /etc/vx/dmpevents.log this time.)   Solution In order Disk /dev/xxxx doen't contain a valid partition table. # fdisk -l /dev/sdyyy .. .. Then establish the BCV LUNs, wait for them to be synchronized with Standard Device, and then split the BCV LUNs. # symmir -g emcdiskgroup establish # symmir -g emcdiskgroup query # symmir -g To the operating system, the volumes created by VxVM look and act like physical disks.

mail ! After this, you'll find the DMP device turned it's state from 'auto - - nolabel' to 'auto:none - - online invalid', and vxdisk list no longer showed the DMP device as IBM ID:*Need an IBM ID? But don't panic this time.

ResourcesLearn For a comparison of AIX and Veritas Volume Manager concepts, read the White Paper "AIX Logical Volume Manager and Veritas Volume Manager quick reference."See the Veritas Volume Manager 3.2 User's Using vxdg to destroy unwanted disk group entry#cd /etc/vx/bin # vxdisk -e list DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME Disk_0 auto - - online hdisk15 Disk_1 auto - - online hdisk14 VxVM overcomes physical restrictions imposed by hardware disk devices by providing a logical volume management layer that lets volumes span multiple disks. To fix, you need to get the steps from EMC to recreate the disk with the correct device links on db1 (ie: so it creates the wd device correctly for the

vxconfigd# vxconfigd -k # vxdisk scandisks # lspv hdisk26 00cc17cec566971d rootvg active hdisk27 00cc17ceebb54c8c rootvg active hdisk28 none None hdisk29 none VeritasVolumes hdisk30 none None hdisk31 none None hdisk32 none VeritasVolumes Adding hdisks into Veritas Volume data group(vxvmdg)# for i in 7 8 9 10 11 12 13 14; do > vxdg -g vxvmdg adddisk vxvmdg$j=hdisk$i > (( j += 1 )) Romeo _______________________________________________ Veritas-vx maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx Previous message View by thread View by date Next message [Veritas-vx] vxdisk list shows disk in error status Romeo Theriault Re: [Veritas-vx] vxdisk list vxconfigd -k ----- Original Message ---- From: joel To: [email protected] Sent: Saturday, 18 July, 2009 11:27:06 AM Subject: [Veritas-vx] vxdisk path question/concern So I had an issue the other night

Romeo Theriault Re: [Veritas-vx] vxdisk list shows disk in error stat... Non-XIV Devices -------------------- Device -------------------- /dev/vx/dmp/disk_0 -------------------- /dev/vx/dmp/disk_1 -------------------- /dev/vx/dmp/disk_2 -------------------- /dev/vx/dmp/disk_3 -------------------- 6. 'vxdisk list' will now show the DMP device(xiv0_18) as 'auto - - nolabel', obviously we should now Or they may be added as nohotuses to be excluded from hot-relocation use. so what you should check is, whether the disk is labelled from OS ?

The VM disk is assigned to one physical disk.Figure 5. rm /dev/vx/dmp/* 3. The server, which is using SVM for the localdisk, needed more swap space so I created a partition on the drive which appeared to be unused and then added the partition May be worth checking these are ok in Solaris.

so the problem confines to db1 node ... Displaying disks in a disk array Data can be spread across several disks within an array to distribute or balance I/O operations across the disks. You haven't mentioned your version of Powerpath, from memory it was meant to be fixed in PowerPath 5.3, but you need to confirm/verify this with EMC. Check the currrent status of the device to be reused# vxdisk list | egrep "DEVICE|LVM|error" DEVICE TYPE DISK GROUP STATUS sdxxx auto - - error sdyyy auto - - LVM  #

Thanks. Thank You! Article:000083058 Publish: Article URL:http://www.veritas.com/docs/000083058 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in Please provide the following output from both db1 and db2: # powermt display dev=emcpower0 # prtvtoc /dev/rdsk/emcpower0c # ls -la /dev/*dsk/emcpower0* If it's a terabyte disk it would have an EFI

A disk group name can be up to 31 characters long. precheck to ensure the removed devices are not part of an existing physical volumes or volume groups # pvs ( Report information about physical volumes ) # vgs ( Report information vxdisk command output# vxdisk list DEVICE TYPE DISK GROUP STATUS Disk_0 auto:none - - online invalid Disk_1 auto:none - - online invalid Disk_2 auto:cdsdisk vxvmdg8 vxvmdg online Disk_3 auto:cdsdisk vxvmdg7 vxvmdg Disk in rootdg group failed, so it was replaced.

At this point, the best bet is to: 1. Each subdisk represents a specific portion of a VM disk, which is mapped to a specific region of a physical disk. Not a big deal but I would like to get rid of the error state and remove the drive from Veritas's knowledge so it shows up like the other local drives, No Yes Did this article save you the trouble of contacting technical support?

vxlicinst command outputInstall License:- # /sbin/vxlicinst Symantec License Manager vxlicinst utility version 3.02.16.0 Copyright (C) 1996-2006 Symantec Corporation. The physical disk device name varies with the computer system you use. A Darren Dunham Re: [Veritas-vx] vxdisk list shows disk in error ... Also would be worth to find with serial number on what is the name of that same disk on db2 node ?

Each volume records and retrieves data from one or more physical disks. It is possible that updates have been made to the original version after this document was translated and published. Solved! Before a disk can be brought under VxVM control, the disk must be accessible through the operating system device interface.