volume stops on 1.4.1;10.4.10: OpHangLimitSecs exceeded

Question

Level 2

490 points

volume stops on 1.4.1;10.4.10: OpHangLimitSecs exceeded

On MDC volume stops.

nssdebug:
1126 13:23:57] 0xa000ed88 (debug) FSS 'OMEGAsan' REGISTERED -> DYING, next event in 60s

system.log:
Nov 26 13:23:46 metadata3 fsm 537: PANIC: /Library/Filesystems/Xsan/bin/fsm "OpHangLimitSecs exceeded VOP-Class-0 Type-17 Subtype-0 183.50 secs Conn[15] Thread-0x187d200 Pqueue-0x304378 Workp-0x94c5818 MsgQ-0x94c5808 Msg-0x94c5864 now 0x43fd4092e29a4 started 0x43fd3fe3e2db3 limit 180 secs.\n" file queues.c, line 612\n

cvlog:
1126 13:17:05.202576] 0x1839000 (Debug) InodeOpen: inode/0x9165b8 too many retries/50, allowing open
1126 13:17:50.350521] 0x183a000 (Debug) InodeOpen: inode/0x9165b8 too many retries/50, allowing open
1126 13:18:43.739563] 0x183b000 (Debug) InodeOpen: inode/0x9165b8 too many retries/50, allowing open
1126 13:20:42.960685] 0xa000ed88 (Debug) Node 15 omegatv_2.server.eo:49353] connected.
1126 13:20:42.981031] 0x187d200 (Debug) Killing stale connection 14 omegatv_2.server.eo:60518.
1126 13:23:46] 0x1809a00 ( *FATAL*) PANIC: /Library/Filesystems/Xsan/bin/fsm "OpHangLimitSecs exceeded VOP-Class-0 Type-17 Subtype-0 183.50 secs Conn 15 Thread-0x187d200 Pqueue-0x304378 Workp-0x94c5818 MsgQ-0x94c5808 Msg-0x94c5864 now 0x43fd4092e29a4 started 0x43fd3fe3e2db3 limit 180 secs.
" file queues.c, line 612
1126 13:23:46.483098] 0xa000ed88 (Debug) Listener_thread: flushing journal.
1126 13:23:46.483148] 0xa000ed88 (Debug) Listener_thread: journal flush complete.
1126 13:23:46] 0x1809a00 ( *FATAL*) PANIC: aborting threads now.

These problems are found by other customers on [http://www.xsanity.com/forum/viewtopic.php?t=579]
No solutions described there.

Tech background: xsan 1.4.1 osx 10.4.10 on G5 dual 2,3 GHz 2 GB internal memory

Mac OS X (10.4.10), GUI? I don't need no stinking gui!

Posted on Nov 26, 2007 6:04 AM

Reply

Answer 1

Nov 29, 2007 3:29 AM in response to Donald Kok

I have exactly the same problem on xsan 1.4.2 and macosx 10.4.11, except in my case all fsm service craches. This began to happen after 1.4.1->1.4.2 and 10.4.10->10.4.11 update respectively. Anyone?

OP-Class-0 Type-3 Subtype-0 183.47 secs Conn[31] Thread-0x187d400 Pqueue-0x3026c8 Workp-0xdf40818 MsgQ-0xdf40808 Msg-0xdf4086
4 now 0x4400e2d57beba started 0x4400e226832ca limit 180 secs. " file queues.c, line 612
Nov 29 11:45:41 xserve2 KernelEventAgent[37]: tid 00000000 received VQ_NOTRESP event (1)
Nov 29 11:45:41 xserve2 servermgrd: xsan: [41/302DD0] ERROR: get fsmvol_atindex: Could not connect to FSM because Admin Tap
Connection to FSM failed. - Bad file descriptor
Nov 29 11:45:41 xserve2 KernelEventAgent[37]: tid 00000000 type 'acfs', mounted on '/Volumes/EditSAN', from '/dev/disk9', not
responding
Nov 29 11:45:41 xserve2 KernelEventAgent[37]: tid 00000000 found 1 filesystem(s) with problem(s)
Nov 29 11:45:41 xserve2 fsm[268]: PANIC: /Library/Filesystems/Xsan/bin/fsm "OpHangLimitSecs exceeded VOP-Class-0 Type-3 Subty
pe-0 183.47 secs Conn[31] Thread-0x187d400 Pqueue-0x3026c8 Workp-0xdf40818 MsgQ-0xdf40808 Msg-0xdf40864 now 0x4400e2d57beba s
tarted 0x4400e226832ca limit 180 secs.\n" file queues.c, line 612\n

and later

Nov 29 11:52:37 xserve2 crashdump[456]: fsm crashed
Nov 29 11:52:37 xserve2 crashdump[456]: crash report written to: /Library/Logs/CrashReporter/fsm.crash.log

Message was edited by: Vilius Šumskas

Reply