verstehe fehlermeldung in /var/log/vmkernel nicht

[adeba]

hallo, kann mir jemand auf "deutsch" sagen, was da grad passiert ist?

Nov 18 11:25:23 svmesx06 vmkernel: 103:03:32:49.541 cpu5:1423)<4>lpfc1:0749:FPe:Completed Abort Task Set Data: x3 x1 x128
Nov 18 11:25:23 svmesx06 vmkernel: 103:03:32:49.541 cpu5:1423)<4>lpfc1:0712:FPe:SCSI layer issued abort device Data: x3 x2
Nov 18 11:25:23 svmesx06 vmkernel: 103:03:32:49.541 cpu5:1029)StorageMonitor: 196: vmhba1:3:1:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:23 svmesx06 vmkernel: 103:03:32:49.613 cpu5:1029)SCSI: 638: Queue for device vml.0200010000600601605cb02100f8c0ab886419de11524149442035 is being
blocked to check for hung SP.
Nov 18 11:25:24 svmesx06 vmkernel: 103:03:32:50.810 cpu5:1423)<4>lpfc1:0749:FPe:Completed Abort Task Set Data: x3 x2 x128
Nov 18 11:25:24 svmesx06 vmkernel: 103:03:32:50.810 cpu5:1366)StorageMonitor: 196: vmhba1:3:2:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:24 svmesx06 vmkernel: 103:03:32:50.810 cpu5:1366)SCSI: 638: Queue for device vml.0200020000600601605cb0210028105b335c61de11524149442035 is being
blocked to check for hung SP.
Nov 18 11:25:47 svmesx06 vmkernel: 103:03:33:13.579 cpu3:1133)<4>lpfc1:0712:FPe:SCSI layer issued abort device Data: x3 x0
Nov 18 11:25:48 svmesx06 vmkernel: 103:03:33:14.840 cpu3:1133)<4>lpfc1:0749:FPe:Completed Abort Task Set Data: x3 x0 x128
Nov 18 11:25:48 svmesx06 vmkernel: 103:03:33:14.840 cpu3:1133)StorageMonitor: 196: vmhba1:3:0:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:48 svmesx06 vmkernel: 103:03:33:15.009 cpu2:1354)SCSI: 638: Queue for device vml.0200000000600601605cb021000c63c29c4c19de11524149442035 is being
blocked to check for hung SP.
Nov 18 11:25:49 svmesx06 vmkernel: 103:03:33:15.242 cpu4:1133)<4>lpfc1:0712:FPe:SCSI layer issued abort device Data: x3 x0
Nov 18 11:25:50 svmesx06 vmkernel: 103:03:33:16.503 cpu5:1133)<4>lpfc1:0749:FPe:Completed Abort Task Set Data: x3 x0 x128
Nov 18 11:25:50 svmesx06 vmkernel: 103:03:33:16.503 cpu5:1133)StorageMonitor: 196: vmhba1:3:0:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:50 svmesx06 vmkernel: 103:03:33:16.904 cpu6:1133)<4>lpfc1:0712:FPe:SCSI layer issued abort device Data: x3 x0
Nov 18 11:25:51 svmesx06 vmkernel: 103:03:33:17.489 cpu0:1039)SCSI: 638: Queue for device vml.0200000000600601605cb021000c63c29c4c19de11524149442035 is being
blocked to check for hung SP.
Nov 18 11:25:52 svmesx06 vmkernel: 103:03:33:18.165 cpu6:1133)<4>lpfc1:0749:FPe:Completed Abort Task Set Data: x3 x0 x128
Nov 18 11:25:52 svmesx06 vmkernel: 103:03:33:18.165 cpu6:1133)StorageMonitor: 196: vmhba1:3:0:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:52 svmesx06 vmkernel: 103:03:33:18.566 cpu5:1133)<4>lpfc1:0712:FPe:SCSI layer issued abort device Data: x3 x0
Nov 18 11:25:53 svmesx06 vmkernel: 103:03:33:19.827 cpu5:1133)<4>lpfc1:0749:FPe:Completed Abort Task Set Data: x3 x0 x128
Nov 18 11:25:53 svmesx06 vmkernel: 103:03:33:19.827 cpu5:1133)StorageMonitor: 196: vmhba1:3:0:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:54 svmesx06 vmkernel: 103:03:33:20.228 cpu6:1133)<4>lpfc1:0712:FPe:SCSI layer issued abort device Data: x3 x0
Nov 18 11:25:54 svmesx06 vmkernel: 103:03:33:20.256 cpu6:1677)SCSI: 638: Queue for device vml.0200000000600601605cb021000c63c29c4c19de11524149442035 is being
blocked to check for hung SP.
Nov 18 11:25:55 svmesx06 vmkernel: 103:03:33:21.488 cpu6:1133)<4>lpfc1:0749:FPe:Completed Abort Task Set Data: x3 x0 x128
Nov 18 11:25:55 svmesx06 vmkernel: 103:03:33:21.488 cpu6:1133)StorageMonitor: 196: vmhba1:3:0:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:55 svmesx06 vmkernel: 103:03:33:21.889 cpu4:1133)<4>lpfc1:0712:FPe:SCSI layer issued abort device Data: x3 x0
Nov 18 11:25:56 svmesx06 vmkernel: 103:03:33:22.987 cpu4:1678)SCSI: 638: Queue for device vml.0200000000600601605cb021000c63c29c4c19de11524149442035 is being
blocked to check for hung SP.
Nov 18 11:25:56 svmesx06 vmkernel: 103:03:33:23.150 cpu7:1133)<4>lpfc1:0749:FPe:Completed Abort Task Set Data: x3 x0 x128
Nov 18 11:25:56 svmesx06 vmkernel: 103:03:33:23.150 cpu7:1133)StorageMonitor: 196: vmhba1:3:0:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.551 cpu7:1133)SCSI: 638: Queue for device vml.0200000000600601605cb021000c63c29c4c19de11524149442035 is being
blocked to check for hung SP.
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6a62aa0 x98 x351ea2f4 xd
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6a62ca8 x98 x351ea2f4 xe
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ac2078 x98 x351ea2f5 xf
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ac2280 x98 x351ea305 x10
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ac2488 x98 x351ea305 x11
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ac2690 x98 x351ea305 x12
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ac2898 x98 x351ea305 x13
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ac2aa0 x98 x351ea305 x14
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ac2ca8 x98 x351ea305 x15
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ae0080 x98 x351ea305 x16
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ae0288 x98 x351ea305 x17
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ae0490 x98 x351ea305 x18
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ae0698 x98 x351ea305 x19
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ae08a0 x98 x351ea305 x1a
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ae0aa8 x98 x351ea305 x1b
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6ae0cb0 x98 x351ea305 x1c
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6abe078 x98 x351ea305 x1d
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6abe280 x98 x351ea305 x1e
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6abe488 x98 x351ea305 x1f
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6abe690 x98 x351ea305 x20
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6abe898 x98 x351ea305 x21
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6abeaa0 x98 x351ea305 x22
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6abeca8 x98 x351ea305 x23
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6a9c080 x98 x351ea305 x24
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6a9c288 x98 x351ea305 x25
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6a9c490 x98 x351ea305 x26
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6a9c698 x98 x351ea305 x27
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6a9c8a0 x98 x351ea305 x28
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6a9caa8 x98 x351ea305 x29
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6a9ccb0 x98 x351ea305 x2a
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6b02078 x98 x351ea305 x2b
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6b02280 x98 x351ea305 x2c
Nov 18 11:25:57 svmesx06 vmkernel: 103:03:33:23.758 cpu4:1502)<4>lpfc1:0754:FPe:SCSI timeout Data: x6b02488 x98 x351ea376 x67
Nov 18 11:25:58 svmesx06 vmkernel: 103:03:33:24.758 cpu0:1024)StorageMonitor: 196: vmhba1:3:1:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:58 svmesx06 last message repeated 2 times
Nov 18 11:25:58 svmesx06 vmkernel: 103:03:33:24.758 cpu0:1024)StorageMonitor: 196: vmhba1:3:2:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:58 svmesx06 last message repeated 3 times
Nov 18 11:25:58 svmesx06 vmkernel: 103:03:33:24.759 cpu0:1024)StorageMonitor: 196: vmhba1:3:2:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:58 svmesx06 last message repeated 7 times
Nov 18 11:25:58 svmesx06 vmkernel: 103:03:33:24.760 cpu0:1024)StorageMonitor: 196: vmhba1:3:2:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:58 svmesx06 last message repeated 16 times
Nov 18 11:25:58 svmesx06 vmkernel: 103:03:33:24.760 cpu0:1024)StorageMonitor: 196: vmhba1:3:1:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:25:58 svmesx06 vmkernel: 103:03:33:25.015 cpu2:1105)SCSI: 638: Queue for device vml.0200010000600601605cb02100f8c0ab886419de11524149442035 is being
blocked to check for hung SP.
Nov 18 11:25:59 svmesx06 vmkernel: 103:03:33:25.163 cpu7:1502)SCSI: 638: Queue for device vml.0200020000600601605cb0210028105b335c61de11524149442035 is being
blocked to check for hung SP.
Nov 18 11:26:07 svmesx06 vmkernel: 103:03:33:33.759 cpu4:1028)<4>lpfc1:0754:FPe:SCSI timeout Data: x6b02898 x98 x351ea3cd x6b
Nov 18 11:26:08 svmesx06 vmkernel: 103:03:33:34.759 cpu0:1024)StorageMonitor: 196: vmhba1:3:1:0 status = 0/7 0x0 0x0 0x0
Nov 18 11:26:09 svmesx06 vmkernel: 103:03:33:35.166 cpu1:1334)SCSI: 638: Queue for device vml.0200010000600601605cb02100f8c0ab886419de11524149442035 is being
blocked to check for hung SP.
[root@svmesx06 root]#

[irix]

Ein "SP" ist ein StorageProcessor. Frage hast du da ein SAN und wenn ja hat das ectl. Problem?

Gruss
Joerg

[adeba]

danke für die info. ja, als san benutze ich eine clarion von emc2. genaues modell ist leider nicht bekannt, da der speicher extern betreut wird. da habe ich nichts mit zu tun. ich werde mal beobachten, ob sich so etwas wiederholt, wenn nicht kann ich mich beruhigt heute abend schlafen legen, oder?

[irix]

Also frueher... zo 3.0.x Zeiten hatte man durchaus Login Timeouts sowie Queue erhoeht fuer seine HBAs.

Guck halt man deinen HBA an. Aber mein Rat waere es das zusammen mit dem StorageAdmin zumachen weil es gehoeren immer 2 dazu

Gruss
Joerg