Sponsored Content
Full Discussion: VxVM and MPxIO
Special Forums Hardware Filesystems, Disks and Memory VxVM and MPxIO Post 302312461 by bluescreen on Friday 1st of May 2009 12:34:50 PM
Old 05-01-2009
VxVM and MPxIO

Smilie

Last week I read that VxVM won't work with MPxIO (i don't recall the link) and that it should be unconfigured when installing VxVM. Today I read that VxVM works in "pass-thru" mode with MPxIO and DMP uses the devices presented by MPxIO.

If I create disks with MPxIO and use VxVM to create volumes for my DBAs, do I get reduced functionality/reliability if something fails? -OR- Should I install VxVM (or the broader package: Veritas Storage Foundation for Oracle RAC) and use the Dynamic multi-pathing (DMP) without MPxIO?


Thanks is Advance!
 

10 More Discussions You Might Find Interesting

1. Solaris

Mpxio

Hi All, I have one question. I found out that my system setting for mpxio-disable=yes. Sun recommend to change it to mpxio-disable=no and run stmsboot -e command. But no one can tell will it affect the system or not and the system is sol-10 and using veritas volume manager and attached... (3 Replies)
Discussion started by: mailbox80
3 Replies

2. Solaris

Mpxio

Hi, I have a quick question. How can I see MPXIO statistics (like errors, how many I/O|throuput per path, ....) on Solaris 10? Does maybe a ready dtrace script exist (I do not have the knowledge to write one myself)? I would be happy if somebody knows some good documentation/links (with... (1 Reply)
Discussion started by: victorinox
1 Replies

3. Filesystems, Disks and Memory

MPxIO question

Greetings Forumers!! I was given a T2000 with one, dual port, HBA card. The card had one fiber connection to the SAN and the former admin enabled MPxIO. Yesterday, I learned that the other port was connected to the same SAN. This system is in another city so I don't have physical access to... (1 Reply)
Discussion started by: bluescreen
1 Replies

4. UNIX for Advanced & Expert Users

mpxio in Solaris10 with NetApp FAS3140 problem

we have a v440 SUN machine with a NetApp FAS3140 SAN storage, the v440 got 2 HBA qlogic cards both connected to the switch side in NetApp 3140, zoning in netapp configured proberly and luns are adversitesed to the SUN machine, the problem i am facing is that when i try to configure the mpxio i am... (7 Replies)
Discussion started by: q8devilish
7 Replies

5. Solaris

MPXIO

Hi Kudo, I wanna to know that how can I do mpxio device name to os native name mapping without using stmsboot -L I tried everything still not able to got the solution till I able to get these o/p here is native disk info as well physical wat is the logical OS name of the disk ... (1 Reply)
Discussion started by: tarunn.dubeyy
1 Replies

6. Solaris

Curious MPxIO problem

Hello folks, I have a newly installed Solaris 10 system running on a T6320 blade. I have set up LDM with the intent to move an ldom from another blade to this one. So far, so good. I had the SAN folks make the LUNs belonging to the ldom visible to my new blade and I can see them, all 4 paths.... (4 Replies)
Discussion started by: Ranck
4 Replies

7. Solaris

Migrate from MPXIO to Powerpath

Here is the issue: I am building a database server using Solaris 10x86 U8. The system is jumpstarted with mpxio enabled and booting from the san. We need to have powerpath 5.3 installed and would like to have powerpath take control of the the boot san as well or have mpxio control the san... (2 Replies)
Discussion started by: nabru72
2 Replies

8. Solaris

solaris turn off multipath mpxio

Im not able to turn the multipath off on the solaris s10 X86...since im on FC boot.. if i disable multipath , from /kernel/drv/iscsi.conf then im not able to boot the machine.:wall: Is there any other go or any suggestions . (2 Replies)
Discussion started by: gowtham.varma
2 Replies

9. Solaris

Solaris 10 + mpxio Path

Hi, I have an Oracle/Sun T3-2 Server with a duel SAS controller Fujitsu DX60 array attached. I have 2 x SAS HBA's in the T3-2. One HBA cabled to CM0 and one HBA cabled to CM1 of the array. The array is setup with one RAID GROUP and one VOLUME and one LUN In Solaris I can see one device... (4 Replies)
Discussion started by: general_lee
4 Replies

10. Solaris

MPxIO Multipathing Problem

Hi, I believe this is an OS multipathing issue - Solaris 10 We have x2 Dual port 8GB Qlogic HBA's installed in our SOlaris 10 host. HBA0 (IOU0) Port WWN's - 09f4 (pci@3,700000/SUNW,qlc@0) 09f5 (pci@3,700000/SUNW,qlc@0,1) HBA1 (IOU1) Port WWN's... (2 Replies)
Discussion started by: jamba1
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)
All times are GMT -4. The time now is 10:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy