NT Security Index inode is bad.

Moe's picture

Have this issue in an Xsan installation

The volume stopped working, running cvfsck -nv gives

[code]*Fatal*: The file system NT Security Index inode is bad.

  • Fatal*: Please run this program in interactive mode to repair this error/code

After I run in interactive mode, it still gives the same error

I've tried varies cvfsck flags, still no use

Any help is appreciated

Moe's picture

In cvlog , if I start the volume, this is what I get at the end

[code][0730 19:58:55] 0xb8eb1000 (Warning) FSM Alloc: Stripe Group "Video" 33753856 free blocks in 169575 fragments inserted.
[0730 19:58:55] 0xb8eb1000 (Warning) FSM Alloc: Stripe Group "Video" 292417 free blocks in 35064 fragments ignored.
[0730 19:58:55] 0xb8eb1000 (Info) FSM Alloc: free blocks 33753856 with 0 blocks currently reserved for client delayed buffers.Reserved blocks may change with client activity.
[0730 19:58:55] 0xb8eb1000 (Info) FSM Alloc: Stripe Group "Video" active.
[0730 19:58:55] 0xa077f720 (**FATAL**) PANIC: /Library/Filesystems/Xsan/bin/fsm ASSERT failed "!error || error == VOP_ENOENT" file ntsecurity.c, line 2103
[0730 19:58:55] 0xa077f720 (**FATAL**) PANIC: wait 3 secs for journal to flush
[0730 19:58:58] 0xa077f720 (**FATAL**) PANIC: aborting threads now.
Logger_thread: sleeps/16 signals/0 flushes/6 writes/6 switches 0
Logger_thread: logged/37 clean/37 toss/0 signalled/0 toss_message/0
Logger_thread: waited/0 awakened/0/code

Moe's picture

After more cvfsck and disabling quotas in the config file, the error in the log file changed to

[code][0730 20:47:40] 0xa077f720 (**FATAL**) PANIC: /Library/Filesystems/Xsan/bin/fsm ASSERT failed "ntsec_sd_access(sdkey, buf, NULL) == 0" file ntsecurity.c, line 2108
/code

cvfsck doesn't report errors, but the volume doesn't start and gives the error above

returnofxsan's picture

You could try disabling ACLs for the volume. Maybe get a second opinion but I think only native extended attributes and case insensitivity settings are irreversible. You'd have to redo all the ACLs afterward.

Moe's picture

returnofxsan wrote:
You could try disabling ACLs for the volume. Maybe get a second opinion but I think only native extended attributes and case insensitivity settings are irreversible. You'd have to redo all the ACLs afterward./quote

I should have mentioned that I disabled ACLs, NT Security and Quotas