This discussion is locked
Bob-0
Level 1 (0 points)

Q: Xsan clients not mounting

Having issues with our Xsan not mounting on all the client machine we have. I can access the metadata controller and the XSAN volume mounts on the MetaData Controller computer. The other weird thing is that on the MDC the fsm and syslogd processes are running unusually high.

When I checked the logs I constantly get
"xsanmdc fsm[105]: Xsan FSS 'SANBox[0]': New connection accept failed - [errno 24]: Too many open files" with
"xsanmdc servermgrd[97641]: xsan: [97641/103B90] ERROR: getquotas_for_fsmvolnamed(SANBox): Could not connect to FSM because Could not find File System Manager for "SANBox" on 10.0.10.2"

Looking back at the logs this I saw this this log entry, which seems to have started this whole thing. Because the log entries before that look normal.
"xsanmdc servermgrd[97641]: xsan: [97641/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because Admin Tap Connection to FSM failed: [errno 60]: Operation timed out"

Another thing that was going on was that there was a client that kept duplicating itself in the XSAN admin. I went in and removed the offending client computer.

Any help and advice would be appreciated.

Mac OS X (10.6)

Posted on Apr 7, 2011 5:19 PM

Close
Bob-0

Q: Xsan clients not mounting

  • All replies
  • Helpful answers

  • by jmyres,

    jmyres jmyres Apr 8, 2011 12:12 AM in response to Bob-0
    Level 1 (80 points)
    Apr 8, 2011 12:12 AM in response to Bob-0
    You may have what are called corrupt free inodes. Inodes are the actual containers in the file system that store your data. Here are some similar threads that may help you:

    http://www.xsanity.com/forum/viewtopic.php?p=3521
    http://www.xsanity.com/forum/viewtopic.php?p=4408

    In the first thread, they were able to simply rebuild their Xsan and restore from backup, but in the second, they were able to use cvfsck -C to perform a "clobber" which removes the bad inodes, so new, uncorrupted inodes can be created.

    The problem is, if you have an Xsan with this kind of corruption, it will usually re-appear, so your best bet is to do what you have to to get your volume back online long enough to grab your data, then re-create your volume again from scratch. If you did a volume expansion in the past without running cvfsck and making sure your file system was clean first, this kind of corruption will sometimes happen.

    Without seeing more, this is all just a guess, but if you find that corrupt inodes are what you're running into, here are some notes from when I've had to fix this myself:

    http://www.jasonmyres.com/2010/11/xsan-2-0-troubleshooting/

    Good luck.

    JM

  • by Bob-0,

    Bob-0 Bob-0 Apr 8, 2011 7:55 PM in response to jmyres
    Level 1 (0 points)
    Apr 8, 2011 7:55 PM in response to jmyres
    Thanks for the advice.
    Ended up hard rebooting the MDC.
    Ran cvfsck after it booted and it came out clean.