Sponsored Content
Operating Systems Solaris Veritas VxVm 3.2 - Cannot unrelocate subdisk due to overlap with existing subdisks Post 302487249 by rajan_g4 on Tuesday 11th of January 2011 08:08:14 PM
Old 01-11-2011
Veritas VxVm 3.2 - Cannot unrelocate subdisk due to overlap with existing subdisks

Hi all,

New to this forum as well as the world of Veritas Volume Manager. My client is using VxVM 3.2. We just changed one of the disk which is under veritas control. I used the appropriate options in vxdiskadm to replace this failed disk. Now when I am trying to unrelocate subdisks back to the original disk, its giving me the following error:

Code:
Error: vxunreloc Subdisk globald05-01 can not be unrelocated to globald08 because it would overlap with the existing subdisks


My vxdiskadm o/p ( after I select option 14 to unrelocate subdisk ) is as follows:

Code:
Move hot-relocated subdisks back to a disk
Menu: VolumeManager/Disk/UnrelocateDisk 
 
Use this operation to move subdisks which were hot-relocated back onto the original disk that has been replaced due to a disk failure. 
This operation takes, as input, the original disk name. If the failed drive was replaced with a disk using a different name, this operation also provides an option to specify the new name.
 
Enter the original disk name [<disk>,list,q,?] list
 
globald01
globald07
globald08
 
Enter the original disk name [<disk>,list,q,?]


Please help !!

Cheers

Raj

Last edited by pludi; 01-12-2011 at 03:47 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

WARNING: VxVM vxio V-5-0-2 Subdisk disk04-28 block 6654400: Uncorrectable read error

Hi , i am new to the veritas volume manager.i saw some message in /var/ad/messages like " WARNING: VxVM vxio V-5-0-2 Subdisk disk04-28 block 6654400: Uncorrectable read error".the disk04 is c2t4d0s2. i have issued some commands iostat,vxdisk list,vxprint -ht .In vxprint -ht i got a message... (1 Reply)
Discussion started by: rjay.com
1 Replies

2. UNIX for Advanced & Expert Users

Veritas VxVM & Vxfs to SVM and UFS

Hi, I have 2 hosts with Veritas VxVM and VxFS (5.0 MP3_RP2). I need to use the application filesystem's luns from these 2 hosts and mount it on another 2 hosts that are running Solaris 9 09/05 and SVM. Is there resources online or has someone tried this? (0 Replies)
Discussion started by: xor
0 Replies

3. Solaris

Veritas VxVM & Vxfs to SVM and UFS

Hi, I have 2 hosts with Veritas VxVM and VxFS (5.0 MP3_RP2). I need to use the application filesystem's luns from these 2 hosts and mount it on another 2 hosts that are running Solaris 9 09/05 and SVM. Is there resources online or has someone tried this? (4 Replies)
Discussion started by: xor
4 Replies

4. Solaris

Symantec/Veritas Volume Manager - subdisk * not in configuration

Hello, There once was a disk. Veritas thought it wasn't happy, but it really was. The disk was all alone on a plex. There was another plex, in the same volume, that was fine and happy with its own single disk. I removed the plex with the unhappy disk. Then I went into vxdiskadm, removed... (2 Replies)
Discussion started by: kity1kity
2 Replies

5. Red Hat

Partition Overlap

I have just purchased a new server running RHELS R6 from a well known supplier. The OS came pre-installed so I (as a previous almost identical server) just finished off the install. I have just been extending one of the partitions and noticed an overlap. Filesystem Size Used Avail... (5 Replies)
Discussion started by: zetex
5 Replies

6. Solaris

Urgent !! SVM, subdisks "UNEXPEXTED INCONSITENCY; RUN fsck MANUALLY

Hi, I am getting this error while server booting up, not sure how to fix this. Unable to mount these file systems /dev/md/rdsk/d51: No such device or address Can't open /dev/md/rdsk/d51: No such device or address /dev/md/rdsk/d51: CAN'T CHECK FILE SYSTEM. /dev/md/rdsk/d51: UNEXPECTED... (1 Reply)
Discussion started by: bobby320
1 Replies

7. Solaris

suncluster co-existing with Veritas Cluster

have a pair of sun servers, wanting to test drive a 2-node cluster using both software.. would like disable one of these cluster software while the othe is running.. Is it feasible at all ?? (2 Replies)
Discussion started by: ppchu99
2 Replies

8. Solaris

VCS Crashing due to inconsistency in opt (managed by VxvM)

We have a Sun Server running Solaris 10 and Veritas Cluster Server. The RAID Volumes in the Server (/ , swap, opt, var, usr) are managed by VxVm and UFS is grown on all these volumes. Lately the system has been crashing due to an inconsistency in the opt filesystem. Upon reboot we did a fsck on... (1 Reply)
Discussion started by: aji1729
1 Replies

9. Shell Programming and Scripting

Finding the Overlap

Hi Help, I am trying to find a overlap zone by compraing th etwo files which is printed below. File-1 is --- 1011 234 2967 787 235 900 435 654 File 2 is --- 1211 456 595 678 546 678 2967 787 I would like to have a o/p which just read 2967 787,'comm' doesn't seem to do the... (5 Replies)
Discussion started by: Indra2011
5 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
vxiod(1M)																 vxiod(1M)

NAME
vxiod - start, stop, and report on Veritas Volume Manager I/O threads SYNOPSIS
vxiod vxiod [-f ] [set count] DESCRIPTION
The vxiod utility starts, stops, or reports on Veritas Volume Manager (VxVM) I/O kernel threads. An I/O thread provides a process context for performing I/O in VxVM. When the vxio module is loaded, 16 I/O threads are created, plus 2 threads per additional CPU for a system with more than 8 CPUs, up to a maximum of 64 threads. At least one I/O thread must be running while the vxio module is loaded, and the number of I/O threads cannot be forced to zero. When invoked with no arguments, vxiod prints the current number of I/O threads to the standard output. The number of threads that is required for handling I/O requests depends on the system load and usage. If volume recovery seems to proceed more slowly at times, it may be possible to improve its performance by increasing the number of I/O threads up to a maximum of 64. KEYWORDS
set When invoked with the set keyword, vxiod creates the number of I/O threads specified by count. If more volume I/O threads exist than are specified by count, the excess processes terminate. If more than the maximum number(64) are specified, the requested number is silently truncated to that maximum. OPTIONS
-f This option has no effect from release 5.0 onward. The number of I/O threads cannot be reduced to zero. EXIT CODES
The vxiod utility prints a diagnostic on the standard error, and exits if an error is encountered. If an I/O request occurs within a I/O thread, the state of that I/O request is not reflected in the exit status for vxiod. Otherwise, vxiod returns a non-zero exit status on error. Usage errors result in an exit status of 1 and a usage message. If the requested number of threads cannot be created, the exit status is 2, and the number of threads that were successfully started is reported. If any other error occurs, the exit status is 3. FILES
/dev/vx/iod The device used to report on and start volume I/O threads. NOTES
Veritas Volume Manager I/O threads cannot be killed directly through the use of signals. Depending on the operating system, VxVM I/O threads may not appear in the list of processes that is output by the ps command. The number of I/O threads that is currently running can be determined by running vxiod. SEE ALSO
fork(2), ps(1), vxconfigd(1M), vxdctl(1M), vxintro(1M), vxio(7), vxiod(7) VxVM 5.0.31.1 24 Mar 2008 vxiod(1M)
All times are GMT -4. The time now is 03:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy