Hello,
I have Xsan network with 2 FSM controllers (xserve1 and xserve2 both PPC servers).
I don't know why but yesterday strange things began to happen. Controller with highest priority (xserve2) failovered to xserve1. I tried to correct this by failovering it manually back to xserve2. I succedded. But after half an hour of work FSM on xserve2 crached with:
OP-Class-0 Type-3 Subtype-0 183.47 secs Conn31 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 KernelEventAgent37: tid 00000000 received VQ_NOTRESP event (1)
Nov 29 11:45:41 xserve2 servermgrd: xsan: 41/302DD0 ERROR: get_fsmvol_at_index: Could not connect to FSM because Admin Tap
Connection to FSM failed. - Bad file descriptor
Nov 29 11:45:41 xserve2 KernelEventAgent37: tid 00000000 type 'acfs', mounted on '/Volumes/EditSAN', from '/dev/disk9', not
responding
Nov 29 11:45:41 xserve2 KernelEventAgent37: tid 00000000 found 1 filesystem(s) with problem(s)
Nov 29 11:45:41 xserve2 fsm268: PANIC: /Library/Filesystems/Xsan/bin/fsm "OpHangLimitSecs exceeded VOP-Class-0 Type-3 Subty
pe-0 183.47 secs Conn31 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 crashdump456: fsm crashed
Nov 29 11:52:37 xserve2 crashdump456: crash report written to: /Library/Logs/CrashReporter/fsm.crash.log
------ Fsm.crash.log content ----
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xb168de3e
So controller failovered to xserve1. And again after couple of minutes of work FSM crached there too with exactly the same error.
I tried everything. Switching of both servers completely and turning back on doesn't helped. Again it starts normally but after random time span FSM craches and failovers to other then it craches too.
Also I tried to to check Xsan filesystem on all XserveRAIDs. It is clean and completely working.
The only thing that helped (at least for now) is moving FSM to completely new Intel based server (xserve3).
Could Xsan 1.4.2 or MacOSX 10.4.11 be a problem here? I installed them couple of weeks ago. But everything worked fine till yesterday.
Please advice! If more logs are needed I would gladly provide it.
--
Best Regards,
Vilius Šumskas
LNK TV IT manager
mob.: +370 614 75713
http://www.lnk.lt
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden
