Using Solaris 10 with Veritas Storage Foundation running. I want to copy all contents from DISKA LUN1 to DISKB LUN2. What would be the command syntax to do this?
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Hello,
We are considering storage migration for RAC database servers(using ASM) from VMAX to VNX?
Any good/bad pointers in this regards please.
Best regards,
Vishal (1 Reply)
Hi all,
I'm in a situation which i need to understand the best way of doing a migration of storage involved in a zone.Elements involved are solaris 10 (Generic_144488-08), metasets. I need to provision more storage to the said non-global zone and not aware of the "best practices" from the ... (2 Replies)
Hi
I have some practical experience with VERITAS Volume Manager and File System. Now I want to appear for VERITAS Storage Foundation 5.0 certification. From my previous experience with Solaris certification I can say that some kind of preparation with sample/practice questions would be highly... (0 Replies)
HI friends,
i'm planning tot study VERITAS Storage Foundation 5.0 .but i didn't get the study meterial (pdf or URL link). Any one can help me to get the PDF .
Rgds,
Jay (4 Replies)
Hi.
I've been working with UNIX/Linux for several years, but never in a VSF environment where I actually got to use any of it.
I downloaded the basic package for free (Don't worry, Symantec now allows for this for limited use) and intend to try this out on Linux and Solaris (also not my... (2 Replies)
...I have a situation where I disks that I mirrored using Solstice Disksuite now need mirroring under Veritas Volume manager...would anyone know the best way to go about 'un-mirroring' and then removing SDS? I can see references in /etc/vfstab and /etc/system that I guess would need... (2 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)