Hi

 

getting some wierd and disturbing errors in the log

 

May 25 10:08:17 Tower kernel: XFS (md9): Internal error xfs_dir_ino_validate at line 224 of file fs/xfs/libxfs/xfs_dir2.c. Caller xfs_dir2_sf_verify+0x6a/0x1c5 [xfs]
May 25 10:08:17 Tower kernel: CPU: 7 PID: 8943 Comm: shfs Not tainted 4.14.40-unRAID #1
May 25 10:08:17 Tower kernel: Hardware name: MSI MS-7885/X99A SLI PLUS(MS-7885), BIOS 1.D0 07/15/2016
May 25 10:08:17 Tower kernel: Call Trace:
May 25 10:08:17 Tower kernel: dump_stack+0x5d/0x79

 

Anyone got any idea?

 

tower-diagnostics-20180525-1011.zip

Check filesystem on disk9, unless this is a returning issue it's probably just a little filesystem corruption, from an unclean shutdown, etc.

 

https://lime-technology.com/wiki/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

This is what i got after i ran a check on disk 9

 

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 entry "" in shortform directory 8594108554 references invalid inode 64739253237559434 entry contains offset out of order in shortform dir 8594108554 junking entry "" in directory inode 8594108554 entry "-." in shortform directory 8594108554 references invalid inode 4503606069821564 junking entry "-." in directory inode 8594108554 entry "" in shortform directory 8594108554 references invalid inode 20548016897261568 entry #0 is zero length in shortform dir 8594108554, junking 4 entries corrected entry count in directory 8594108554, was 4, now 0 corrected i8 count in directory 8594108554, was 6, now 0 corrected directory 8594108554 size, was 299, now 6 corrected entry offsets in directory 8594108554 bogus .. inode number (0) in directory inode 8594108554, clearing inode number - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 2 - agno = 4 - agno = 0 - agno = 5 - agno = 3 - agno = 1 bogus .. inode number (0) in directory inode 8594108554, clearing inode number - agno = 6 - agno = 7 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... entry "Season 04" in dir ino 6442451068 doesn't have a .. entry, will set it in ino 8594108554. Invalid inode number 0x0 xfs_dir_ino_validate: XFS_ERROR_REPORT fatal error -- couldn't map inode 8594108554, err = 117

 

If i remove the -n tag and run the check again nothing happens.....

Run xfs_repair (without -n) on the command line:

 

https://lime-technology.com/wiki/Check_Disk_Filesystems#Drives_formatted_with_XFS