VxFS volume wont go online
Hello,
I create a SAN volume and want to create a VxFS volume but the volume manager disables the device again and again.
Apr 30 15:41:20 cassia last message repeated 1 time
Apr 30 15:41:22 cassia vxdmp: [ID 736771 kern.notice] NOTICE: VxVM vxdmp V-5-0-148 enabled path 31/0x240 belonging to the dmpnode 205/0x40
Apr 30 15:41:22 cassia vxdmp: [ID 899070 kern.notice] NOTICE: VxVM vxdmp V-5-0-147 enabled dmpnode 205/0x40
Apr 30 15:41:22 cassia vxdmp: [ID 480808 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 31/0x240 belonging to the dmpnode 205/0x40 due to open failure
Apr 30 15:41:22 cassia vxdmp: [ID 824220 kern.notice] NOTICE: VxVM vxdmp V-5-0-111 disabled dmpnode 205/0x40
Apr 30 15:41:23 cassia vxdmp: [ID 275047 kern.notice] NOTICE: VxVM vxdmp V-5-3-1062 dmp_restore_node: Unstable path 31/0x240 will not be available for I/O until 300 seconds
Apr 30 15:41:23 cassia vxdmp: [ID 238993 kern.notice] NOTICE: VxVM vxdmp 0 dmp_tur_temp_pgr: open failed: error = 6 dev=0xcd/0x42
Apr 30 15:41:23 cassia vxdmp: [ID 954821 kern.notice] NOTICE: VxVM vxdmp V-5-3-1061 dmp_restore_node: The path 31/0x240 has not yet aged - 299
Apr 30 15:41:23 cassia last message repeated 1 time
It is a Solaris box. What could be the cause?
Cheers
Marlen
Comments 5 Comments • Jump to latest comment
Which release of VxVM are you using? Do a "modinfo | grep vx", and get the line for vxdmp. Also, who is the vendor of your disk array, and what is the model of the array?
Have you checked to make sure you have the right ASL/APM software installed for your disk array (if necessary)? Have you verified with the Hardware Compatability List (HCL) doc for your release of VxVM?
Hi,
Anything else in messages files related to disk issues ? Is the device in a non standard state ?
One possibility is that the device is responding to SCSI inquiries but is failing read/write i/o's
cheers
tony
can you give more details of device like prtvtoc output ... also paste a snippet from format output ...
DO you use powerpath or any other multipathing software underneath ?
also give more details on OS version, array model & veritas version ...
Gaurav
PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
I have a HP P2000 SAN on one end and on the other end a Solaris 10 with an Qlogic HBA controller. We currently do not use mutlipathing or anything related to this just single straight connections.
This is my luxadm output briefly:
HBA Port WWN: 21000024ff2cbf37
OS Device Name: /dev/cfg/c3
Manufacturer: QLogic Corp.
Model: 371-4325-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.03; EFI: 2.01;
Serial Number: 0402R00-1047884819
The volume that does not work is a second one that I just tried to add to the host.
I already have a working one on the maschine.
This is the output the SAN gives about the two volumes (the volume sql2 is the new one)
Name Serial Number LUN Access Ports
------------------------------------------------------------------------------
cassia-sql1 00c0ff111f0d0000b81f704d01000000 4 read-write A1,A2,B1,B2
cassia-sql2 00c0ff111f0d00001aa49a4f01000000 1 read-write A1,A2,B1,B2
The errors are found every 5 minutes:
May 3 10:34:09 cassia vxdmp: [ID 736771 kern.notice] NOTICE: VxVM vxdmp V-5-0-148 enabled path 31/0x240 belonging to the dmpnode 205/0x40
May 3 10:34:09 cassia vxdmp: [ID 899070 kern.notice] NOTICE: VxVM vxdmp V-5-0-147 enabled dmpnode 205/0x40
May 3 10:34:09 cassia vxdmp: [ID 480808 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 31/0x240 belonging to the dmpnode 205/0x40 due to open failure
May 3 10:34:09 cassia vxdmp: [ID 824220 kern.notice] NOTICE: VxVM vxdmp V-5-0-111 disabled dmpnode 205/0x40
May 3 10:34:11 cassia vxdmp: [ID 275047 kern.notice] NOTICE: VxVM vxdmp V-5-3-1062 dmp_restore_node: Unstable path 31/0x240 will not be available for I/O until 300 seconds
May 3 10:34:11 cassia vxdmp: [ID 238993 kern.notice] NOTICE: VxVM vxdmp 0 dmp_tur_temp_pgr: open failed: error = 6 dev=0xcd/0x42
May 3 10:34:11 cassia vxdmp: [ID 954821 kern.notice] NOTICE: VxVM vxdmp V-5-3-1061 dmp_restore_node: The path 31/0x240 has not yet aged - 299
May 3 10:34:11 cassia last message repeated 1 time
root@cassia:/var/sadm/patch# prtvtoc /dev/rdsk/c4t600C0FF000111F0D1AA49A4F01000000d0p0
prtvtoc: /dev/rdsk/c4t600C0FF000111F0D1AA49A4F01000000d0p0: Unable to read Disk geometry errno = 0x5
Now: I have changed the LUN from 1 to 11 on the SAN and it seems the system does not get the change of the LUN although I rebooted:
y 3 11:53:27 cassia genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
May 3 11:53:34 cassia scsi: [ID 799468 kern.info] sd9 at scsi_vhci0: name g600c0ff000111f0d1aa49a4f01000000, bus address g600c0ff000111f0d1aa49a4f01000000
May 3 11:53:34 cassia genunix: [ID 936769 kern.info] sd9 is /scsi_vhci/disk@g600c0ff000111f0d1aa49a4f01000000
May 3 11:53:34 cassia genunix: [ID 408114 kern.info] /scsi_vhci/disk@g600c0ff000111f0d1aa49a4f01000000 (sd9) online
May 3 11:53:34 cassia genunix: [ID 834635 kern.info] /scsi_vhci/disk@g600c0ff000111f0d1aa49a4f01000000 (sd9) multipath status: degraded, path /pci@0,0/pci8086,25e2@2/pci8086,3500@0/pci8086,3510@0/pci111d,801c@0/pci111d,801c@2/pci1077,171@0,1/fp@0,0 (fp1) to target address: w207000c0ff111bb2,b is online Load balancing: round-robin
May 3 11:53:39 cassia genunix: [ID 834635 kern.info] /scsi_vhci/disk@g600c0ff000111f0d1aa49a4f01000000 (sd9) multipath status: optimal, path /pci@0,0/pci8086,25e2@2/pci8086,3500@0/pci8086,3510@0/pci111d,801c@0/pci111d,801c@2/pci1077,171@0,1/fp@0,0 (fp1) to target address: w247000c0ff111bb2,b is online Load balancing: round-robin
May 3 11:55:59 cassia vxdmp: [ID 480808 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 31/0x240 belonging to the dmpnode 205/0xc0 due to open failure
May 3 11:55:59 cassia vxdmp: [ID 824220 kern.notice] NOTICE: VxVM vxdmp V-5-0-111 disabled dmpnode 205/0xc0
May 3 11:55:59 cassia vxdmp: [ID 736771 kern.notice] NOTICE: VxVM vxdmp V-5-0-148 enabled path 31/0x240 belonging to the dmpnode 205/0xc0
Format says the following:
AVAILABLE DISK SELECTIONS:
0. c0t0d0
/pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@0,0
1. c0t1d0
/pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@1,0
2. c4t600C0FF000111F0D1AA49A4F01000000d0
/scsi_vhci/disk@g600c0ff000111f0d1aa49a4f01000000
3. c4t600C0FF000111F0DB81F704D01000000d0
/scsi_vhci/disk@g600c0ff000111f0db81f704d01000000
Specify disk (enter its number): 2
selecting c4t600C0FF000111F0D1AA49A4F01000000d0
[disk formatted]
Disk not labeled. Label it now? yes
Warning: error setting drive geometry.
Warning: error writing VTOC.
Warning: no backup labels
Write label failed
Do you also feel the LUN number of the device should be different now?
Although you stated you are not using any multipathing, based on the output you provided above it would appear that MPxIO is configured on this box. When you run format:
2. c4t600C0FF000111F0D1AA49A4F01000000d0 /scsi_vhci/disk@g600c0ff000111f0d1aa49a4f01000000
The only time the device path would read /scsi_vhci is when MPxIO is configured.
(man scsi_vhci for more details)
I would suggest running the following command to disable MPxIO and reboot the box:
stmsboot -d
This will disable MPxIO for all controllers and update your /etc/vfstab with the appropriate disk device.
After which you can then try to label your disk in format.
Hope this helps,
Joe D
Would you like to reply?
Login or Register to post your comment.