Volume Manager 1.3


 
Thread Tools Search this Thread
Operating Systems HP-UX Volume Manager 1.3
# 1  
Old 04-21-2008
Volume Manager 1.3

Hi, I'm getting an error on our Unix box with Veritas Volume Manager v1.3

We are using Unix 7M+ v11 L10 if this makes sense.

We've had to rebuild our Unix box after hard drive failure and this message below keeps appearing:

'Protocol error with Volume Configuration Daemon'.

The volume manager is not allowing the O/S access to the data drives.

Could anyone suggest how I can resolve this;I'm unfamiliar with Unix so any help would be most welcome.

Kind Regards, tim dixon.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

solaris volume manager- stripe?

Hello Admins.. I am going through solaris volume manager guide for RAID-0 concatenation and stripes, I do not understand the concept of stripe from following example of concatenation. There is an eample for concatenation: # metainit d25 1 1 c0t1d0s2 d25: Concat/Stripe is setup the... (5 Replies)
Discussion started by: snchaudhari2
5 Replies

2. UNIX for Dummies Questions & Answers

VERITAS Volume Manager - mirror a disk/volume

I have a machine (5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V210) that we are upgrading the storage and my task is to mirror what is already on the machine to the new disk. I have the disk, it is labeled and ready but I am not sure of the next steps to mirror the existing diskgroup and... (1 Reply)
Discussion started by: rookieuxixsa
1 Replies

3. Solaris

Solaris Volume manager

Hi Friends, I have to migrate my raid-1 volume to raid -5 online. Can anyone please help me, If possible then send me the step by step commands for online migration. Thanks in advance. (2 Replies)
Discussion started by: rajaramrnb
2 Replies

4. Solaris

Regarding Sun volume manager

hi all, i have a doubt. I am doing some R & D in sun volume manager. Sun solaris 5.10 is running in my sun blade 150 sparc machine. I have attached ultrascsi storage box(6x36GB hdd's) with my machine. when i create a raid 0 striping or raid 1 mirroring the output of metastat says Dbase = No. Can... (2 Replies)
Discussion started by: kingston
2 Replies

5. Solaris

vertias volume manager

hi all I want to practice on veritas volume manager. Is there any trial version for solaris 5.10 sparc version. If it is there, please give me the link? (1 Reply)
Discussion started by: kingston
1 Replies

6. Solaris

Solaris Volume Manager

Hello All, I have small doubt. It's related to SVM in solaris 10. I have created raid 0 (striping) using 3 slices of 500 MB size (default interlace value as 32KB) d2: Concat/Stripe ---- Interlace value is 32 KB Size: 2923830 blocks (1.4 GB) Stripe 0: (interlace: 64 blocks) Device Start... (1 Reply)
Discussion started by: vaibhav.kanchan
1 Replies

7. Solaris

RAID manager or veritas volume manager

Can somebody kindly help me to determine which one i should choose to better manipulate OS volume. RAID manager or veritas volume manager? Any critical differences between those two? Thanks in advance. (5 Replies)
Discussion started by: beginningDBA
5 Replies

8. UNIX for Advanced & Expert Users

Regarding Veritas Volume manager

hy guys I am new at this thread , i have installed sf 5.0 and wanted to encapsulate root disk but when i get to optionn to enter private region i get this error: Enter desired private region length (default: 65536) 512 VxVM ERROR V-5-2-338 The encapsulation operation failed with the... (2 Replies)
Discussion started by: charneet
2 Replies

9. Solaris

How to resize mirror volume in veritas volume manager 3.5 on Solaris 9 OE

Hi all, I have a problem with vxvm volume which is mirror with two disks. when i am try to increase file system, it is throwing an ERROR: can not allocate 5083938 blocks, ERROR: can not able to run vxassist on this volume. Please find a sutable solutions. Thanks and Regards B. Nageswar... (0 Replies)
Discussion started by: nageswarb
0 Replies

10. AIX

Logical Volume Manager Help

I have a pretty basic question but I am finding my self stumped... I am trying to find the config that shows which logical volume is mapped to which physical volume IE: I know that pdisk15 is mapped to hdisk17 (I only know this as it was told to me though, by IBM) When I run: lslv -p... (5 Replies)
Discussion started by: pheusion
5 Replies
Login or Register to Ask a Question
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)