Skip navigation
This discussion is archived

XSAN Volume keeps unmounting due to /dev/disk18 not responding

990 Views 5 Replies Latest reply: Sep 4, 2012 5:59 PM by Blaidd Drwg RSS
monching16 Calculating status...
Currently Being Moderated
Aug 28, 2012 12:40 AM

Hi Support and everybody,

 

I would like to ask some technical advice from you.

We have a setup for XSAN Server.

3 -MDC: Mac OS X Server 10.6.6, XSAN 2.2 (xserves)

1-OD: Mac OS X Server 10.6.6, XSAN 2.2 (xserves)

60-Clients: Mac OS X 10.6.6, XSAN 2.2 (macpros)

3 x XSAN Volumes

9 x promise Storages

 

ISSUE: Recently, One of the XSAN Volume keeps unmounting.

           The only way to mount it back is to reboot the whole Xserves and MDC including the Promise storages.

 

According to the MDC Logs: /dev/disk18 is not responding

 

My question is which LUN from the XSAN corresponds to /dev/disk18?

How to isolate the issue?XSANAdminLog.jpg

 

 

 

 

 

 

 

 

Which LUN does /dev/disk18 corresponds?

RaidAdmin.jpg

 

 

 

 

 

 

What does the /dev/disk18 not responding means?

 

 

 

Please advise.

XSAN, XSAN Expansion
  • Blaidd Drwg Level 1 Level 1 (70 points)

    That device number corresponds to the Xsan volume itself. It doesn't correspond to any LUN.

     

    The fsm process that controls the volume is crashing--see the fsm panic messages in the log. Consider stopping the volume then running "cvfsck -nv VolumeName". This will do a read only check for problems with the metadata.

  • Blaidd Drwg Level 1 Level 1 (70 points)

    1. Yes, the -n means read-only.

     

    2. Replace the -n with -w, e.g:

     

    cvfsck -wv VolumeName

  • Blaidd Drwg Level 1 Level 1 (70 points)

    It looks like there were a few errors:

     

    Scanning inodes 307200 ( 29%).      

    *Error*: XATTR ERROR detected for inode 0x529ca63 (0x80000529ca64)

    *Error*: *** RESETTING RPL DATA FOR FILE SYSTEM ***

    Scanning inodes 819200 ( 77%).      

    *Error*: XATTR ERROR detected for inode 0x8b84e71 (0x8b84e73)

    Scanning inodes 1052672 (100%).

     

    cvfsck said the file system was modified, so hopefully it was fixed.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.