This discussion is locked
pspercqr

Q: Xsan volume can not active anymore

Did someone meet this problem before? after San volume can not mount , I check file system ,seems result Not so bad .but still can not active to use . pdc:Xsan xsan$ sudo cvfsck Xsan File Systems on host pdc.local: 1)  Raid1  2)  Raid2  Choose a file system by number (1-2) or zero (0) to exit -> 1 Created directory /tmp/cvfsck396a for temporary files. Creating MetadataAndJournal allocation check file. Creating Data allocation check file. ** NOTE ** Read Only Check. File system journal will not be recovered. The results may be inconsistent and mis-leading. Super Block information.   FS Created On               : Mon Nov 14 13:33:24 2011   Inode Version               : '2.5' - XSan 2.2 named streams inode version (0x205)   File System Status          : Clean   Allocated Inodes            : 364544   Free Inodes                 : 151060   FL Blocks                   : 33   Next Inode Chunk            : 0x7bf4   Metadump Seqno              : 0   Restore Journal Seqno       : 0   Windows Security Indx Inode : 0x5   Windows Security Data Inode : 0x6   Quota Database Inode        : 0x7   ID Database Inode           : 0xa   Client Write Opens Inode    : 0x8 Stripe Group MetadataAndJournal             (  0) 0xba40d0 blocks. Stripe Group Data                           (  1) 0x35d78740 blocks. Building Inode Index Database 364544 (100%).           Verifying NT Security Descriptors Found 108 NT Security Descriptors: all are good Verifying Free List Extents. Scanning inodes 364544 (100%).           Sorting extent list for MetadataAndJournal pass 1/1 Updating bitmap for MetadataAndJournal extents 8095 (  1%).                     Sorting extent list for Data pass 1/1 Updating bitmap for Data extents 465792 (100%).                     Checking for dead inodes 364544 (100%).           Checking directories 8018 (100%).          Scanning for orphaned inodes 364544 (100%).         Verifying link & subdir counts 364544 (100%).           Checking free list. 364544 (100%).          Checking pending free list.                         Checking Arbitration Control Block. Checking MetadataAndJournal allocation bit maps (100%).          Checking Data allocation bit maps (100%).          File system 'Raid1'. Blocks-903317312 free-204862828 Inodes-364544 free-151060. File System Read-Only Check completed successfully. pdc:Xsan xsan$ sudo cvfsck Xsan File Systems on host pdc.local: 1)  Raid1  2)  Raid2  Choose a file system by number (1-2) or zero (0) to exit -> 2 Created directory /tmp/cvfsck479a for temporary files. Creating MetadataAndJournal allocation check file. Creating Data allocation check file. ** NOTE ** Read Only Check. File system journal will not be recovered. The results may be inconsistent and mis-leading. Super Block information.   FS Created On               : Mon Nov 14 13:33:18 2011   Inode Version               : '2.5' - XSan 2.2 named streams inode version (0x205)   File System Status          : Clean   Allocated Inodes            : 824320   Free Inodes                 : 21216   FL Blocks                   : 56   Next Inode Chunk            : 0xd080   Metadump Seqno              : 0   Restore Journal Seqno       : 0   Windows Security Indx Inode : 0x5   Windows Security Data Inode : 0x6   Quota Database Inode        : 0x7   ID Database Inode           : 0xa   Client Write Opens Inode    : 0x8 Stripe Group MetadataAndJournal             (  0) 0xba3d10 blocks. Stripe Group Data                           (  1) 0x35d78740 blocks. Building Inode Index Database 824320 (100%).           Verifying NT Security Descriptors Found 98 NT Security Descriptors: all are good Verifying Free List Extents. Scanning inodes 824320 (100%).           Sorting extent list for MetadataAndJournal pass 1/1 Updating bitmap for MetadataAndJournal extents 14946 (  0%).                     Sorting extent list for Data pass 1/1 Updating bitmap for Data extents 1883317 (100%).                     Checking for dead inodes 824320 (100%).           Checking directories 14139 (100%).          Scanning for orphaned inodes 824320 (100%).         Verifying link & subdir counts 824320 (100%).           Checking free list. 824320 (100%).          Checking pending free list.                         Checking Arbitration Control Block. Checking MetadataAndJournal allocation bit maps (100%).          Checking Data allocation bit maps (100%).          File system 'Raid2'. Blocks-903317312 free-131411393 Inodes-824320 free-21216. Xsanadmin> select List FSS File System Services (* indicates service is in control of FS): No FSSs are active. Xsanadmin> activate Raid1 Activate FSM "Raid1" Could not find File System Manager for "Raid1" on pdc.local. Cannot activate FSS Raid1 Question: how to start file system manager by manually? Is that possible? And I have restore the whole system when Xsan running normal but still this problem!

Mac Pro, Mac OS X (10.7.2)

Posted on Oct 22, 2014 7:27 PM

Close

Q: Xsan volume can not active anymore

  • All replies
  • Helpful answers

  • by Claudio Sanchez1,

    Claudio Sanchez1 Claudio Sanchez1 Oct 23, 2014 11:07 PM in response to pspercqr
    Level 1 (65 points)
    Oct 23, 2014 11:07 PM in response to pspercqr
    Xsanadmin> select
    List FSS File System Services (* indicates service is in control of FS):
    No FSSs are active.
    Xsanadmin> activate Raid1
    Activate FSM "Raid1"
    Could not find File System Manager for "Raid1" on pdc.local. Cannot activate FSS Raid1

    Question: how to start file system manager by manually? Is that possible? And I have restore the whole system when Xsan running normal but still this problem!

    Try "start Raid1" before "activate Raid1".

  • by pspercqr,

    pspercqr pspercqr Oct 23, 2014 11:21 PM in response to Claudio Sanchez1
    Level 1 (0 points)
    Oct 23, 2014 11:21 PM in response to Claudio Sanchez1

    thanks for your quick reply , yes i try the "start" and "activate" also , seems no different , but i fix it after reboot my ethernet switch , the volume was alive again  , because i check the xsan filesystem everything was fine ,so i think the file system manager just a process on the xsan controller  .