11-27-2006
VxVM/Hba cards/Solaris 10 FS issue
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 discovered/available with the SAN.
The Temp solution is to mount manually all the volumes with the following command : vxvol -g loc1vg startall & mountall
The other workaround is to reboot my server each time with the command : reboot -- -r
If I reboot my server with Init 6 :
hba1: QLogic Fibre Channel Host Adapter fcode version 2.00.09
hba1: Firmware v3.3.12 (ipx)
QLogic Fibre Channel Driver v4.20 Instance: 2
hba2: QLogic Fibre Channel Host Adapter fcode version 2.00.09
hba2: Firmware v3.3.12 (ipx)
Hostname: svdlux69
NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk
cpqccl288: found array controller device at tgt32, lun0
cpqccl288: Vendor/Product ID = COMPAQ HSV110 (C)COMPAQ
cpqccl291: found array controller device at tgt35, lun0
cpqccl291: Vendor/Product ID = COMPAQ HSV110 (C)COMPAQ
cpqccl33: found array controller device at tgt33, lun0
cpqccl33: Vendor/Product ID = COMPAQ HSV110 (C)COMPAQ
cpqccl34: found array controller device at tgt34, lun0
cpqccl34: Vendor/Product ID = COMPAQ HSV110 (C)COMPAQ
NOTICE: VxVM vxdmp V-5-0-148 enabled path 118/0x30 belonging to the dmpnode 282/0x18
NOTICE: VxVM vxdmp V-5-0-148 enabled path 118/0x38 belonging to the dmpnode 282/0x10
Nov 22 09:28:45 spagent[418]: Starting spagent.
checking ufs filesystems
/dev/vx/rdsk/bootdg/opt: is clean.
checking vxfs filesystems
Running parallel replay fsck ...
/dev/vx/rdsk/loc1vg/loc1lv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/opttivlv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/tivlv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/ccmslv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/bgslv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/toolslv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/ecclv:file system check failure, aborting ...
/dev/vx/rdsk/loc1vg/crashlv:file system check failure, aborting ...
The following filesystems could not be repaired :
/dev/vx/rdsk/loc1vg/loc1lv
/dev/vx/rdsk/loc1vg/ccmslv
/dev/vx/rdsk/loc1vg/opttivlv
/dev/vx/rdsk/loc1vg/tivlv
/dev/vx/rdsk/loc1vg/toolslv
/dev/vx/rdsk/loc1vg/bgslv
/dev/vx/rdsk/loc1vg/ecclv
/dev/vx/rdsk/loc1vg/crashlv
fsckall failed with exit code 1.
WARNING - Unable to repair one or more filesystems.
Run fsck manually (fsck filesystem...).
I tried to put Sleep commands on all the scripts files (veritas+ Hp) without success ....
Any ideas ??
Thanks,
Fabien
10 More Discussions You Might Find Interesting
1. Solaris
Has anyone ever relocated an HBA card after already having it configured in another PCI slot? I've found that the HBA instance #'s start incrementing past the previous. It results in me having to have my instance numbers in /kernel/drv/qla2300.conf be 4,5,6,7 instead of 0,1,2,3. Cleanup with... (5 Replies)
Discussion started by: kduffin
5 Replies
2. 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
3. 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
4. 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
5. Solaris
Hiii... Every one....
I want to know the command to get the details and number of HBA cards
attached to a server.
I know that we can use "powermt display", but nither my cards are connected to the storage nor powerpath is active.
I am using SUN server with Solaris -9.
Thanks in... (4 Replies)
Discussion started by: Reboot
4 Replies
6. Solaris
Hi,
Quick question if anyone knows this. Is there a command I can use in Veritas Volume manager on Solaris that will tell me what the name of the SAN I am connected to? We have a number of SANs so I am unsure which one my servers are connected to. Thanks. (13 Replies)
Discussion started by: gwhelan
13 Replies
7. 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
8. Solaris
This is going to mean nothing to most....
I'm working on a E4500 server running Solaris 2.5.1 and VXVM 2.5.5 :eek:
I've replaced the rootmirror and would like to monitor progress of the resync
It's only a 2Gb /partition so it shouldn't take too long.
In later versions
vxtask list
... (5 Replies)
Discussion started by: Martincorneuk
5 Replies
9. Red Hat
hi all,
I am trying to view the hba cards on a rhel7 server (storage says they are there, but I am not seeing them.
I tried lspci -nn | grep -i hba
lspci |grep qla
I tried looking in /sys/class/fc_host.. but it is empty.
I am not sure if I am looking in the right spot... (0 Replies)
Discussion started by: gartie
0 Replies
10. Solaris
hi everone
i am experiencing disconnectivity from storage to My database machines. i have doubt on my FC cards in my sparc T4-2 machines. i want to know how should i check from my solaris that whether the cards are ok or not because once the disks get disconnect from SAN so it come back again but... (5 Replies)
Discussion started by: janakors
5 Replies
LEARN ABOUT HPUX
vxvmconvert
vxvmconvert(1M) vxvmconvert(1M)
NAME
vxvmconvert - convert LVM volume groups to VxVM disk groups
SYNOPSIS
vxvmconvert
DESCRIPTION
vxvmconvert is a menu-driven program to convert an HP Logical Volume Manger (LVM) configuration to a Veritas Volume Manager configuration.
This man page is a brief overview of vxvmconvert. Refer to the Veritas Volume Manager Migration Guide for a detailed description before
using the conversion procedure.
The vxvmconvert script is interactive and prompts you for responses, supplying defaults where appropriate. There is a Help facility at
every prompt. Enter a question mark (?) at a prompt to display a context-sensitive help message.
With vxvmconvert you can identify LVM volume groups, list disks, analyze volume groups for conversion and complete the conversion of LVM
volume groups to VxVM disk groups.
LVM configurations are converted at the volume group level. All disks used in a volume group are converted together. You cannot use vxvm-
convert to convert unused LVM disks (those not part of an LVM volume group) to VxVM disks. To convert unused LVM disks, use pvremove to
take the disk out of LVM control, then initialize the disk for VxVM use by using vxdiskadm (see pvremove(1M) and vxdiskadm(1M) for more
information).
vxvmconvert changes disks within LVM volume groups to VxVM disks by replacing the areas of the disks used for LVM configuration information
and with the equivalent VxVM volume configuration information. Portions of the disks used for user data, such as file systems and data-
bases, are not affected by the conversion.
The conversion process changes the names by which your system refers to the logical storage, so must be done offline. No applications can
access data in the volume groups undergoing conversion. You must unmount file systems using those volumes and shut down any applications,
such as databases, that might use the volumes directly.
OPERATIONS
Analyze LVM Volume Groups for Conversion
Use this operation to analyze one or more LVM volume groups for conversion to use by VxVM. The analysis checks for problems that
can prevent the conversion from completing successfully. It calculates the space required to add volume group disks to a Volume
Manager disk group. More than one volume group may be entered at the prompt. A grep-like pattern may be used to select multiple
volume groups.
See the ``Limitations in Conversion'' section in the Volume Manager Migration Guide for more information.
Convert LVM Volume Groups to VxVM
Converts one or more LVM volume groups to one or more VxVM disk groups. This adds the disks to a VxVM disk group and replaces
existing LVM volumes with VxVM volumes.
vxvmconvert prompts you to name the VxVM disk group that replaces the LVM volume group being converted. A default is suggested
at the prompt. For example, if you are converting a volume group vg08, vxvmconvert renames it as dg08.
See to the sections ``Dealing with New Logical Volume Names'' and ``Tailoring your VxVM Configuration'' in the Volume Manager
Migration Guide for more information.
Rollback from VxVM to LVM
Rollback reverts VxVM disk groups to LVM volume groups. vxvmconvert provides a limited snapshot capability for the LVM metadata
in a converted volume group. A snapshot is a simple protection method to use during conversion.
Caution! Do not use this operation if the VxVM disk group was modified since the conversion.
See to the section ``Restoring LVM Volume Groups and Disaster Recovery'' in the Volume Manager Migration Guide for more informa-
tion.
List Disk Information
Displays information about the disks on a system. You can obtain detailed information about a disk by entering a specific disk
device address.
List LVM Volume Group Information
Listvg displays a list of LVM volume groups. You can obtain detailed information about an LVM volume group at a specific disk
device address.
SEE ALSO
pvremove(1M), vgcfgbackup(1M), vgrestore(1M), vxdisk(1M), vxdiskadd(1M), vxdiskadm(1M), vxintro(1M)
Veritas Volume Manager Migration Guide
VxVM 5.0.31.1 24 Mar 2008 vxvmconvert(1M)