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

NAME
vxtrace - trace operations on volumes SYNOPSIS
vxtrace [-aeEls ] [-b buffersize] [-c eventcount] [-d outputfile] [-f inputfile] [-g diskgroup] [-k buffersize] [-m millisec_delay] [-o objtype [,objtype]...] [-t timeout] [-w waitinterval] [name | device]... DESCRIPTION
The vxtrace utility prints kernel error or I/O trace event records on the standard output or writes them to a file in binary format. Binary trace records written to a file can be read back and formatted by vxtrace as well. If no arguments are specified, vxtrace reports either all error trace data or all I/O trace data on all virtual disk devices. With error trace data, it is possible to select all accumulated error trace data, to wait for new error trace data, or both (the default). Selection can be limited to a specific disk group, to specific types of Veritas Volume Manager (VxVM) kernel I/O objects, or to particular named objects or devices. Under heavy loads, the kernel may discard one or more records before they can be reported to vxtrace. Even though the contents of the records are lost, the kernel keeps track of the number of lost records and reports this to vxtrace. as a record. vxtrace displays this record indicating that records were lost. You can increase the size of the kernel buffer using the -k buffersize option to reduce the likelihood of the kernel discarding records. OPTIONS
-a Appends to the outputfile instead of truncating it. By default, the output file is truncated. -b buffersize Sets the size of the buffer used by vxtrace when it obtains trace records from the kernel, or from a file when the -f option is specified. The buffer size is specified as a standard Veritas Volume Manager length (see vxintro(1M)). The default buffer size is 8K. -c eventcount Accumulates at most eventcount events and then exits. The timeout and eventcount options can be used together. -d outputfile Writes (dumps) binary trace data to the specified output file. -e Selects new error trace data. The default is to select I/O trace data. -E Selects pre-existing error trace data. This can be combined with -e to get both pre-existing trace data and new trace data. -f inputfile Reads binary trace data from the specified input file, instead of from the Veritas Volume Manager kernel. -g diskgroup Selects objects from the specified disk group. The disk group can be specified either by disk group ID or by disk group name. With no name or device arguments, all appropriate objects in the disk group are selected. With the name argument, diskgroup specifies the disk group that contains the named configuration record. -k buffersize Sets the kernel I/O trace buffer size. The Veritas Volume Manager kernel allocates a private kernel space to buffer the I/O trace records for each vxtrace command. The default buffer size is 8K bytes. Some trace records may be discarded if the trace buffer is too small. This option can be used to set a larger or a smaller kernel trace buffer size. The buffer size is speci- fied as a standard Veritas Volume Manager length (see vxintro(1M)). Depending on the Veritas Volume Manager kernel configura- tion, usually only a maximum buffer size of 1 megabyte is granted. -l Long format. Prints all available fields for all tracing records, instead of a subset of the available fields. The default is to use the short format. -m millisec_delay Pauses vxtrace for the specified period to allow more records to accumulate. name | device If name or device are specified, Veritas Volume Manager kernel objects of the requested types are selected if they are associated with the configuration records or virtual disk devices indicated by those arguments. -o objtype [,objtype]... Selects object based on the objtype option arguments. Multiple types of objects can be specified with one or several -o options. The possible object selection types are: all | ALL Selects all possible virtual disk devices, kernel objects, and physical disks. dev | logical Selects virtual disk devices. disk | physical Selects Veritas Volume Manager physical disks. log Selects all log objects. logplex Selects RAID-5 log plexes. logsd Selects DRL (dirty region logging) or RAID-5 log subdisks. logvol Selects DRL or RAID-5 log volumes. m | mv | mirror Selects mirrored volume kernel objects. p | pl | plex Selects striped or concatenated plex kernel objects. rl | rlink Selects RLINK kernel objects. If an RVG (replicated volume group) is specified, all RLINKs associated with that RVG are selected. s | sd | subdisk Selects subdisk kernel objects. v | vol | volume Selects mirrored or RAID-5 volume kernel objects. -s Specifies using synchronous writes to the outputfile instead of asynchronous writes. Asynchronous writes is the default. -t timeout Accumulates trace data for at most timeout seconds, then exits. -w waitinterval If vxtrace waits for waitinterval seconds without receiving any new events, prints waiting... to allow scripts to wake up and process previously accumulated events. This is useful for processing errors. The waiting... message does not count as an event for the purposes of the -c option. ARGUMENTS
Arguments specify configuration record names, or physical or virtual disk device nodes (by device path). If no object types were selected with the -o option, only trace records corresponding to the indicated configuration records or devices are selected; otherwise, objects of the requested types are selected if they are associated in any way with the named configuration record or device. If a name argument does not match a regular configuration record, but does match a disk access record, the indicated physical disk is selected. Physical disks can also be selected by the disk media record name. By default, name arguments are searched for in the default disk group (defaultdg) unless a disk group is specified using the -g option. The disk group for any individual name argument can be overridden using the form: diskgroup/recordname Note: When reading trace data from a file with the -f option, association information is not available. EXAMPLES
To trace all physical disk I/Os, enter: vxtrace -o disk To trace virtual disk device I/Os to the device associated with volume testvol, use either of the commands: vxtrace -g testdg -o dev testvol vxtrace /dev/vx/dsk/testdg/testvol To trace all log subdisks associated with volume testvol, enter: vxtrace -g testdg -o logsd testvol To trace all log objects, enter: vxtrace -o log To accumulate ten seconds worth of trace data for disk04 and then format that data, use: vxtrace -t 10 -d /tmp/tracedata disk04 vxtrace -l -f /tmp/tracedata To read error trace data into a script for processing, using ten second pauses to generate mail messages, use the command: vxtrace -leE -w 10 | while read ... FILES
/dev/vx/trace SEE ALSO
vxintro(1M), vxstat(1M), vxtrace(7) VxVM 5.0.31.1 24 Mar 2008 vxtrace(1M)
All times are GMT -4. The time now is 01:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy