This discussion is locked
nnconcerts
Level 1 (0 points)

Q: Xsan Invalid inode lookup.

I am getting a few invalid node lookup messages and the server hung on fsmps process since yesterday. Any reason why this happens and what could be the problem?

Application Specific Information:
PANIC: /Library/Filesystems/Xsan/bin/fsm "OpHangLimitSecs exceeded VOP-Rmdir 183.29 secs Conn[1] Thread-0xb4a23000 Pqueue-0x20dd88 Workp-0xde0e018 MsgQ-0xde0e008 Msg-0xde0e05c now 0x48527350853df started 0x485272a1b92c0 limit 180 secs.
" file queues.c, line 619
And the thread is libSystem.B.dylib


Apr 27 09:21:56 hqwfsx02 fsm[145]: Xsan FSS 'hqwmfs01[0]': Invalid inode lookup: 0x7f80000000c4c0 markers 0x0/0x0 gen 0x0 nextiel 0x0
Apr 27 09:24:10 hqwfsx02 fsm[145]: Xsan FSS 'hqwmfs01[0]': Invalid inode lookup: 0x8973 markers 0x0/0x0 gen 0x0 nextiel 0x0
Apr 27 09:24:40: --- last message repeated 1 time ---
Apr 27 09:25:38 hqwfsx02 fsm[145]: Xsan FSS 'hqwmfs01[0]': Invalid inode lookup: 0x2773 markers 0x0/0x0 gen 0x0 nextiel 0x0
Apr 27 09:25:38: --- last message repeated 1 time ---
Apr 27 09:25:38 hqwfsx02 fsm[145]: Xsan FSS 'hqwmfs01[0]': Invalid inode lookup: 0x7f800000002780 markers 0x0/0x0 gen 0x0 nextiel 0x0
Apr 27 09:25:38 hqwfsx02 fsm[145]: Xsan FSS 'hqwmfs01[0]': Invalid inode lookup: 0x7f8000000027a0 markers 0x4469/0x0 gen 0x0 nextiel 0x0
Apr 27 09:25:38 hqwfsx02 fsm[145]: Xsan FSS 'hqwmfs01[0]': Invalid inode lookup: 0x7f8000000027c0 markers 0x0/0x0 gen 0x0 nextiel 0x0
Apr 27 09:25:38 hqwfsx02 fsm[145]: Xsan FSS 'hqwmfs01[0]': Invalid inode lookup: 0x7f8000000027e0 markers 0x0/0x0 gen 0x0 nextiel 0x0

Mac Server, Mac OS X (10.5.7)

Posted on Apr 27, 2010 9:58 AM

Close
nnconcerts

Q: Xsan Invalid inode lookup.

  • All replies
  • Helpful answers

  • by Moe .,

    Moe . Moe . May 23, 2010 2:57 PM in response to nnconcerts
    Level 1 (10 points)
    May 23, 2010 2:57 PM in response to nnconcerts
    It seems your MDC can't access some of the inodes on the arrays
    I've seen this on some promise raids before, not necessarily promise related

    Probably time to re-examine the arrays
    I'd recommend making regular metadata backup, since this could cause the volume to no mount at some point in the future

    What does cvfsck -nv tell you ?