06-25-2005
Yes, you can find the 66MHz slots on sunsolve.
Also, what are you using for volume management? If using Veritas Volume Manager, there is no need to worry about the controller numbers changing.
If using Sun Disk Suite, I think you will have problems.
10 More Discussions You Might Find Interesting
1. BSD
Hi!
I just wanted to know what network cards are supported in FreeBSD. I have looked at the list of supported cards but I can't find any of them in the stores. Is the list not updated, I would really preciate info about where (in EU, Sweden) I can buy them.
/Peter (2 Replies)
Discussion started by: Barfly.se
2 Replies
2. Solaris
Hi all,
I have a compatibly issues with a new hardware
My config is the following one :
Solaris 10
V490 Hardware
2 X HBA Qlogic 2310f cards
An HP EVA 5000 for storage ...
Veritas VxVM 4.1 MP1
When I reboot my server, VxVM is trying to mount/use the volume before it's... (0 Replies)
Discussion started by: unclefab
0 Replies
3. Solaris
Due to speed mismatch, the server kept crashing. Sun suggests that I need to move the two HBA cards from the 66Mhz to the 33Mhz slots. There are tons of disks that are connected to these HBAs and I have Veritas volume manager.
Does anyone have a list of what I need to do prior/after moving to... (3 Replies)
Discussion started by: kiem
3 Replies
4. Solaris
I've got lots of scsi transport errors on the E2900 - the HBA was replaced once out of curiosity but the problem still exists.
Feb 15 07:03:11 ivsdbch2 scsi: WARNING: /ssm@0,0/pci@18
,600000/SUNW,jfca@1,1/fp@0,0/ssd@w5005076300c889cb,4 (ssd21):
Feb 15 07:03:11 ivsdbch2 SCSI transport... (1 Reply)
Discussion started by: kiem
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (3 Replies)
Discussion started by: ronbarak
3 Replies
6. Solaris
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (4 Replies)
Discussion started by: ronbarak
4 Replies
7. SCO
I'm floundering here trying to locate a PCI-E 1x HBA that will support an external tape drive in SCO Openserver 6. I was unable to find anything that would work in the compatible hardware list and a call to Adaptec confirmed that PCI-X would've been a better option for the risers in the Dell 2950... (1 Reply)
Discussion started by: s_mal
1 Replies
8. Solaris
I'm looking for open PCI slots in our array of sun boxes. I need help on how to distinguish if there's an open slot or not using prtdiag and prtconf. Is there a better tool for this? TIA.
Here's my prtdiag -v | grep pci:
pci 66 PCI5 SUNW,qlc-pci1077,2312 (scsi-+
... (9 Replies)
Discussion started by: revzalot
9 Replies
9. BSD
Hi,
The title is a bit misleading, but it seems I can't re-edit the title after creating the post - apologies.
I have been handed a variety of servers, whereas quite a few of these are older FreeBSD (4.8, thank you legacy). I now have one of these servers which has a HBA card installed, and... (0 Replies)
Discussion started by: brightstorm
0 Replies
10. Solaris
How do I find any available PCI slots on a v440?
When I run prtconf, I get the following output? But I am not able to make out whether all the PCI slots are used.
================================= IO Devices =================================
Bus Freq
Brd Type MHz Slot ... (1 Reply)
Discussion started by: jtamminen
1 Replies
vxiod(7) Miscellaneous Information Manual vxiod(7)
NAME
vxiod - Veritas Volume Manager I/O daemon process control device
DESCRIPTION
The vxiod device in Veritas Volume Manager (VxVM) is used to control the number of volume I/O daemons active on the system. A process con-
text is necessary to implement the plex consistency recovery and writeback error handling policies for multi-plex volumes, and for continu-
ing normal I/O after a log write if the volume has logging enabled. It is also required for the plex recovery performed with a mirrored
volume in the read/writeback mode.
There are three aspects of I/O daemon operations:
o General I/O
o Error handling
o Log handling
I/O handling is achieved by an ioctl command that does not return, but instead calls the vxiod routine to wait for errors or I/O requests
and process them. When an error occurs, if there are no I/O daemons active, the I/O simply turns into a failure on that plex. If a gen-
eral I/O request is queued up when no daemons exist, then the I/O will hang forever until a daemon process is created. If I/O daemons are
active, then the I/O is put on a work queue and the daemons are awakened. A daemon takes an error request and tries to read other plexes
until a read succeeds or all plexes have been tried. Then, if the writeback facility is enabled, the daemon tries to write the good data
to each plex that failed on the read. If the write is successful, the read error is nullified. An I/O request is handled in a similar
manner.
Logging is handled in a similar manner. An ioctl command, which does not return, is issued to create a daemon for each volume which has
logging enabled. This daemon monitors two queues: one queue of I/O which was started while the log was busy (the ``log'' queue), and
another queue of requests which have been logged and now need to be started (the ``ready'' queue). I/O requests are taken from the log
queue when the log is no longer busy, and another log write is started. Completion of a log write results in all I/O requests which have
just been logged being placed on the I/O daemon's ready queue where they are immediately started.
One mechanism finds out how many I/O error daemons are running, and another mechanism allows a process to become an I/O daemon. Before a
process becomes an I/O daemon, it should close all open files and detach from the controlling tty. An I/O or logging daemon cannot be
killed except through an explicit ioctl.
FILES
/dev/vx/iod vxiod control device
SEE ALSO
vxiod(1M), ioctl(2)
VxVM 5.0.31.1 24 Mar 2008 vxiod(7)