Sponsored Content
Operating Systems Solaris ( VxVM ) How to add the removed disk back to previous disk group Post 302308379 by waibabe on Saturday 18th of April 2009 01:09:50 AM
Old 04-18-2009
( VxVM ) How to add the removed disk back to previous disk group

Previously , i remove the disk by

#vxdg -g testdg -k rmdisk testdg02

But i got error when i -k adddisk



bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c0t1d0s2 auto:none - - online invalid
c4t129d0s2 auto:cdsdisk - - online
c4t129d1s2 auto:cdsdisk testdg01 testdg online
- - testdg02 testdg removed was:c4t129d0s2


bash-2.03# vxdg -g testdg -k adddisk testdg02=c4t129d0

VxVM vxdg ERROR V-5-1-2349 Device c4t129d0s2 appears to be owned by disk group testdg.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

VxVM disk/lun grow

hi, i have a volume on a LUN of an EMC-storage and i need to increase the size. i could increase the size of the LUN on the EMC, i could increase the size of the disk for solaris, but how can i tell the veritas volume manager that the disk is larger now? what i've done: 1. LUN on EMC 2.... (3 Replies)
Discussion started by: pressy
3 Replies

2. Solaris

How to add disk into Striped Volume VxVM

VxVM: How to add one more disk into v08 the stripe should change from 7/128 to 8/128 v v08 - ENABLED ACTIVE 8954292224 SELECT v08-01 fsgen pl v08-01 v08 ENABLED ACTIVE 8954292480 STRIPE 7/128 RW sd bkpdg35-01 v08-01 bkpdg35 17216 ... (0 Replies)
Discussion started by: geoffry
0 Replies

3. Solaris

Migrate VxVM boot disks to higher capacity disk

Hi, Im getting a downtime of 4 hrs to do porting of bootdisks. Currently, the system is running on Sf4800. 2 internal disk 36G connected to a SE3510 storage. We're getting 72G disks and we want to restore the OS from the current 36G to the 72G disk. System is under veritas volume manager ctrl.... (4 Replies)
Discussion started by: incredible
4 Replies

4. Solaris

vxvm root disk booting problem - solved with boot -a. How?

Hi All, We had a Sun Netra T1 go down the other day, the root disk was mirrored using vxvm. Upon boot from either disk, we had the following error appear: WARNING: Error writing ufs log state WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run... (4 Replies)
Discussion started by: badoshi
4 Replies

5. Solaris

Disk Storage Need to Add more Disk

Hi, Anyone can help me, just want to confirm, if possible adding a disk storage that we have a RAWDATA with +ASM in our database. If possible, what would you recommend "workaround used" from us to do and the preparation. And also how long the downtime will take. Our disk continuous to grow,... (0 Replies)
Discussion started by: fpalero
0 Replies

6. Solaris

Unable to add disk to VG group.

Hi, I am new to solaris administration. I have scan the new EMC SAN disk. I am able to see the disk when i run the powermt display dev=all command o/p. I want to format the disk and add file system to that disk. Can have formated the disk. and this the o/p of my format bash-3.00# prtvtoc... (3 Replies)
Discussion started by: jpkumar10
3 Replies

7. Solaris

Unable to boot from mirror disk on x86 server configured under VxVM

Hi, Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot. vxplex -g rootdg dis var-02 vxplex -g rootdg dis swapvol-02 vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies

8. Emergency UNIX and Linux Support

VxVM not able to see new disk

I have VxVM 5.1 running on Solaris-10. I have to increase a application file-system and storage team gave me a lun. After scanning scsi port by cfgadm, I can see them in format output. I labelled it, but I am not able to see them in "vxdisk list". I already tried commands --> vxdctl enable... (4 Replies)
Discussion started by: solaris_1977
4 Replies

9. HP-UX

Removing a VxVM disk from a Disk Group

Hello all, So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'` do rmsf -H $i done I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 Replies

10. Solaris

How to clear a removed single-disk pool from being listed by zpool import?

On an OmniOS server, I removed a single-disk pool I was using for testing. Now, when I run zpool import it will show it as FAULTED, since that single disk not available anymore. # zpool import pool: fido id: 7452075738474086658 state: FAULTED status: The pool was last... (11 Replies)
Discussion started by: priyadarshan
11 Replies
vxdiskadm(1M)															     vxdiskadm(1M)

NAME
vxdiskadm - menu-driven Veritas Volume Manager disk administrator SYNOPSIS
vxdiskadm DESCRIPTION
vxdiskadm provides a menu-driven interface to perform common Veritas Volume Manager (VxVM) disk administration tasks. The vxdiskadm script is interactive and prompts you for responses, supplying defaults where appropriate. Help is available at every prompt by entering a question mark (?) to display a context-sensitive help message. To add disks, specify one or more disks with a disk-address-pattern-list. The basic format for disk addresses is c#t#d# or enclosure-based names such as enc1_0. You can specify just the controller and target to add all the disks at that SCSI address. For example, use c2t0 to specify all disks on controller two, target zero. You can specify more than one disk address or address pattern on the command line. The word all specifies all disks on the system. Disk address names relate directly to device node names in the /dev/dsk and /dev/rdsk directo- ries. You can use the files /etc/vx/disks.exclude, /etc/vx/cntrls.exclude and /etc/vx/enclr.exclude to exclude disks, controllers and enclosures from use by vxdiskadm. Each line of disks.exclude specifies a disk to exclude, for example, c0t3d0. Each line of cntrls.exclude specifies the address of a controller to exclude, for example, c2. Each line of enclr.exclude specifies an enclosure to be excluded, for example, enc1. OPERATIONS
Add or initialize one or more disks Prompts for one or more disk device addresses, and a disk group to which these are to be added. When initializing disks into a new disk group, you are prompted to choose whether this disk group should be compatible with the Cross-platform Data Sharing (CDS) feature. You are also given the alternative of initializing the disk but leaving it unallocated to a disk group. A default disk name is assigned with the format, diskgroup##, such that the names are unique within all imported disk groups. You are prompted to specify whether to designate the disks as spares for the disk group. Remove a disk Prompts for a disk, by disk media name. The disk is checked to ensure that no subdisks reside on the disk. If the disk is in use, the operation fails with a recommendation to first move all volumes off the disk. If this disk is the last disk in a group, you are also prompted whether to remove the disk group from the system. The operation then calls vxdg rmdisk to remove the disk from its disk group. If this is the last disk in its disk group, vxdg deport is used instead. Remove a disk for replacement Prompts for a disk by disk media name. The disk is checked for volumes that would lose all mirrors as a result of the operation. If such volumes exist, those volumes are listed and you are prompted whether to continue the operation. The operation calls vxdg -k rmdisk to dissociate the media record from the physical disk. If there are formatted disks available that have disk headers but no disk group, you are prompted whether to use one of these disks as a replacement. Replace a failed or removed disk Prompts for a disk media name. The named media record must be dissociated from a disk. If the media record is not in the removed state, unused disks are scanned for matching disk IDs. If a disk with a matching disk ID is found, you are prompted whether to reattach that disk. If a matching disk is not used, you are prompted for a new disk, by device address. If the named replacement disk has a valid disk header, but is not allocated to a disk group, you are prompted whether to reinitialize the disk. If the named replacement disk is listed as allocated to a disk group or to another host, you are prompted whether to continue the operation. If the device is initialized, vxdisksetup is called to set up public and private regions and to create the disk header. Given an initialized disk, the operation replaces the disk in a disk group with vxdg -k adddisk. Mirror volumes on a disk Prompts for a disk, by media name. It then prompts for a destination disk within the same disk group, also by media name. Spec- ifying no destination disks indicates that any disk can be the destination. The operation calls vxmirror to mirror the volumes. Move volumes from a disk Prompts for a disk, by media name. It then prompts for a possible list of destination disks, also by disk media name. Specify- ing no destination disks indicates that any disk is suitable. The operation calls vxevac to move subdisks off the disk. Enable access to (import) a disk group Prompts for a disk group name. The operation calls vxdg import to import the disk group stored on that disk. Remove access to (deport) a disk group Prompts for a disk group name. The prompt lists alternate disk groups and the disks (media name and access name) that they con- tain. The operation calls vxdg deport. Enable (online) a disk device Prompts for a disk device. The prompt lets you display the disks on the system. The operation functions only for disks cur- rently offline. It then makes the disk accessible. Disable (offline) a disk device Prompts for a disk device. The prompt lets you display the disks on the system. The operation functions only for disks cur- rently online, but not part of any disk group. It then marks the disk as offline such that VxVM no longer tries to access the disk. Mark a disk as a spare for a disk group Sets up a disk as a spare device for its disk group. A spare disk can be used to automatically replace a disk that has failed. No space can be used on a disk that is marked as a spare. Turn off the spare flag for a disk Removes a disk from the list of spare disks, and returns its space to the general pool of available space. Remove (deport) and destroy a disk group Removes access to and destroys a disk group that is currently enabled (imported). A disk group may be destroyed if the disks are needed for some other purpose. Unrelocate subdisks back to a disk Moves subdisks which were hot-relocated following a disk failure back to the original disk, or to a disk with a different name, possibly with a different offset. Exclude a disk from hot-relocation use Sets up a disk to be excluded from use by hot-relocation. The disk is marked as nohotuse and it cannot be used by hot-relocation to replace a disk that has failed. However, it remains available to be used as free space for its disk group. Make a disk available for hot-relocation use Turns off the nohotuse flag on a disk. Use this option to make a disk available for hot-relocation use. This only applies to disks that were previously excluded from hot-relocation use. Prevent multipathing/Suppress devices from VxVM's view Excludes devices from VxVM's view, or prevents them from being multipathed by the dynamic multipathing (DMP) driver, vxdmp. There are three ways of specifying the devices on which these operations are to be performed: o As a controller for all devices connected through the controller. o As a physical pathname for all devices under that path. o As a combination of the Vendor ID and Product ID (VID:PID) for all devices of that type. This option also provides a method to define pathgroups in case of disks which are not multipathed by VxVM. Only one path from a pathgroup will be made visible to VxVM. This is useful to avoid duplicate entries for devices that are not multipathed by vxdmp. Allow multipathing/Unsuppress devices from VxVM's view Makes devices visible to VxVM again or makes vxdmp multipath these devices again. This can be performed only on devices that have already been specified using the "Prevent multipathing/Suppress devices from VxVM's view" option. List currently suppressed/non-multipathed devices Lists all devices suppressed from VxVM's view and all devices prevented from being multipathed by vxdmp. Change the disk naming scheme Changes the disk naming scheme from the c#t#d# format to enclosure-based. Alternatively, if the existing naming scheme is enclo- sure-based, it is changed to c#t#d# format. Note: Changing to enclosure-based naming may cause the failure of persistent disk access records for simple or nopriv disks. You can use the vxdarestore utility to repair these records. See the vxdarestore(1M) manual page for more information. This option is equivalent to using the vxddladm set namingscheme={ebn|osn} command. Note: Devices with very long device names (for example, Fibre Channel devices that include worldwide name (WWN) identifiers) are always represented by enclosure-based names. This operation has no effect on such devices. Change/Display the default disk layouts Allows you to change or display the default disk format and private region length that are used when initializing disks. Mark a disk as allocator-reserved for a disk group Reserves a disk for use with the Intelligent Storage Provisioning (ISP) feature when allocating storage space. Turn off the allocator-reserved flag on a disk Allows space on a disk to be allocated by VxVM commands other those provided with the Intelligent Storage Provisioning feature. List disk information Displays a list of disks. You can also choose to list detailed information about the disk at a specific disk device address. Hardware-Specific Note Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM follows the guidelines when adding disks to disk groups and when mirroring the volumes on a disk. If the operation fails due to these guideline(s), you are prompted to use the force option. The force option ignores any such storage-specific guidelines. FILES
/etc/vx/cntrls.exclude Specifies the address of controllers to exclude from vxdiskadm operations. /etc/vx/disks.exclude Specifies the address of disks to exclude from vxdiskadm operations. /etc/vx/enclr.exclude Specifies the names of enclosures to exclude from vxdiskadm operations. NOTES
EFI disks cannot be added to a disk group that is compatible with the Cross-platform Data Sharing (CDS) feature, nor can they be formatted as CDS disks. See the vxddladm(1M) manual page for information on using the vxddladm command to include or exclude specific array libraries from device discovery. SEE ALSO
vxdarestore(1M), vxddladm(1M), vxdg(1M), vxdisk(1M), vxdiskadd(1M), vxdisksetup(1M), vxevac(1M), vxintro(1M) VxVM 5.0.31.1 24 Mar 2008 vxdiskadm(1M)
All times are GMT -4. The time now is 08:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy