Sponsored Content
Operating Systems Solaris Need to remove a disk from Veritas Post 302113277 by reborg on Wednesday 4th of April 2007 02:00:39 PM
Old 04-04-2007
if you're sure it's really bogus:

Make sure there are no dead plexes hanging around, and remove them if there are.

You can check with
Code:
vxprint -pg hpdg | grep NODEVICE

Column 2 is plex name. If there are some dead plexes, disassociate and remove them:
Code:
vxplex -g hpdg -o rm dis <plex name>

Then vxedit the disk out of hpdg:
Code:
vxedit -g hpdg -rf rm disk

 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

FSCK on veritas managed disk

I've had a VXFS filesystem get corrupted and now it won't mount. Can I run a fsck -y on the raw disk device or should something be done within veritas? Veritas does not see the disk at the moment. (2 Replies)
Discussion started by: ozzmosiz
2 Replies

2. Solaris

Veritas root disk mirroring

Hi there, My task is to replace the two 73 G disks with two 143 G disks , which has vxvm 4.1 running on it. I would like to know whether the steps iam following are correct. 1. Break the sub-disks, plexes of the root mirror. 2. Remove the sub-disks,plexes of the root mirror. 3. Remove one of... (10 Replies)
Discussion started by: Jartan
10 Replies

3. Shell Programming and Scripting

mapping device from an inq output to veritas disk groups

Hi, Does anyone have a clever way of mapping the following from two different files using perl. sample line from vxdisk list output (vxdisk-list.file): emcpower18s2 auto:sliced IDFAG1_1 (IDFAG1_appdg) online sample line from 'inq' output (inq.file): ... (0 Replies)
Discussion started by: csoesan
0 Replies

4. UNIX and Linux Applications

Veritas silent disk group creation

I am trying to write a kornshell script that will automatically create veritas disk groups. However, the only utility that I can find that will create the diskgroup is vxdiskadd, which prompts with interactive questions. I've tried to pass the answers through to vxdiskadd, but I receive the... (0 Replies)
Discussion started by: jm6601
0 Replies

5. Solaris

Help needed to find out the disk controller for veritas disks

hi all i am using vxvm 5.1 on my sun blade 150 which is running with solaris 5.10. When i give the command "vxdisk list" it gives the following output # vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online... (2 Replies)
Discussion started by: kingston
2 Replies

6. AIX

Remove internal disk from Veritas Control

I installed new internal disks in my p570. They will be part of a new AIX vg. Unfortunately, we have Veritas Volume Manager running on this AIX 5.2 ml 10 box. Veritas has grabbed control of the disks. I want AIX LVM to control the disks. I cannot get these disks free of Veritas: <lspv... (2 Replies)
Discussion started by: BobSmith
2 Replies

7. UNIX for Dummies Questions & Answers

Configure disk group with veritas

People i have an a storage i create two virtual disk 1 y 2. In the virtual disk 1 i configure 8 volumes and in the Vd2 configure 5 volumes. Now i want to create a disk group called Prod2 y Dev2 but when i go to vxdiskadm and i choose add disk o encapusalte when i press list to list the disk... (0 Replies)
Discussion started by: enkei17
0 Replies

8. Solaris

Veritas not attaching replaced disk

Hi, I`m on SunFire480R with Solaris 10. Disk in rootdg group failed, so it was replaced. However, I cannot make Veritas initalise the replaced disk: # vxdctl enable # vxdisk list c1t0d0s2 Device: c1t0d0s2 devicetag: c1t0d0 type: auto flags: online error private autoconfig... (1 Reply)
Discussion started by: masloff
1 Replies

9. Solaris

Veritas disk group not the same on each cluster node.

Need help getting all disk devices back on node 2 the same as node 1. Recently Veritas and/or Sun cluster got wrecked on my 2 node Sun cluster after installing the latest patch cluster. I backed out the patches and then node 2 could see only half of the devices and Veritas drives (though format... (0 Replies)
Discussion started by: buggin
0 Replies

10. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
volrecover(8)						      System Manager's Manual						     volrecover(8)

NAME
volrecover - Performs volume recovery operations SYNOPSIS
/sbin/volrecover [-g diskgroup] [-sb] [-o options] [volume | medianame...] OPTIONS
Options that can be specified to volrecover are: Starts disabled volumes that are selected by the operation. Volumes will be started before any other recovery actions are taken. Volumes will be started with the -o delayrecover start option. This requests that any opera- tions that can be delayed in starting a volume will be delayed. In other words, only those operations necessary to make a volume available for use will occur. Other operations, such as mirror resynchronization, attaching of stale plexes and subdisks, and recovery of stale RAID5 parity will normally be delayed. Performs recovery operations in the background. With this option, volrecover will put itself in the back- ground to attach stale plexes and subdisks, and to resynchronize mirrored volumes and RAID5 parity. If this is used with -s, volumes will be started before recovery begins in the background. Performs no recovery operations. If used with -s, volumes will be started, but no other actions will be taken. If used with -p, the only action of volrecover will be to print a list of startable volumes. Prints the list of selected volumes that are startable. For each startable volume, a line is printed containing the following information: the volume name, the disk group ID of the volume, the volume's usage type, and a list of state flags pertaining to mirrors of the volume. State flags and their meanings are: One of the mirrors was detached by an I/O failure One of the mirrors needs recovery, but the recovery is related to an administrative operation, not an I/O failure Neither kdetach nor stale is appropriate for the volume. Displays information about each task started by volrecover. For recovery operations (as opposed to start operations), a completion status is printed when each task completes. Displays commands that volrecover would execute without actually executing them. Lim- its operation of the command to the given disk group, as specified by disk group ID or disk group name. If no volume or medianame operands are given, all disks in this disk group will be recovered; otherwise, the volume and medianame operands will be evaluated relative to the given disk group. Without the -g option, if no operands are given, all volumes in all imported disk groups will be recovered; otherwise, the disk group for each medianame operand will be determined based on name uniqueness within all disk groups. Passes the given option argu- ments to the -o options for the volplex att and volume start operations generated by volrecover. An option argument of the form pre- fix:options can be specified to restrict the set of commands that the -o option should be applied to. Defined prefixes are: Applies to all invocations of the volume utility (volume starts, mirror resynchronizations, RAID5 partity rebuilds, and RAID5 subdisk recoveries) Applies to all invocations of the volplex utility (currently used only for attaching plexes) Applies specifically to plex attach operations applies specifically to volume start operations Applies to subdisk recoveries Applies to mirror resynchronization and RAID5 parity recovery DESCRIPTION
The volrecover program performs plex attach, RAID5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (medianame). If no medianame or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). If -s is specified, disabled volumes will be started. With -s and -n, volumes are started, but no other recovery takes place. Recovery operations will be started in an order that prevents two concurrent operations from involving the same disk. Operations that involve unrelated disks will run in parallel. EXAMPLES
To recover, in the background, any detached subdisks or plexes that resulted from replacement of a specified disk, use the command: # volrecover -b medianame If you want to monitor the operations, use the command: # volrecover -v medianame SEE ALSO
volintro(8), volplex(8), volume(8) volrecover(8)
All times are GMT -4. The time now is 02:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy