[solved] Do I have XFS corruption on my cache partition or no?

[Chunks]

Edit afterwards: the output from "dmesg" is not updated until you reboot. I must have fixed the errors but not seen it. A reboot cleared them from dmesg.

---

 

I was tinkering with an unrelated issue, when I stumbled upon XFS errors.

 

Specifically, I was using

dmesg

to try to figure out if/where my bluetooth device was As I was scrolling around, I saw a big red block of text:

[  499.522570] XFS (nvme0n1p1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x5d1948 dinode
[  499.526457] XFS (nvme0n1p1): Unmount and run xfs_repair
[  499.530281] XFS (nvme0n1p1): First 128 bytes of corrupted metadata buffer:
[  499.534110] 00000000: 49 4e 81 ed 03 02 00 00 00 00 00 63 00 00 00 64  IN.........c...d
[  499.538029] 00000010: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  499.541922] 00000020: 66 16 cc 9c 0e c6 a0 a9 66 16 cc 9c 0e e5 25 4b  f.......f.....%K
[  499.545811] 00000030: 66 43 1b b8 18 8d a5 60 00 00 00 00 00 03 8e a0  fC.....`........
[  499.549700] 00000040: 00 00 00 00 00 00 00 39 00 00 00 00 00 00 00 01  .......9........
[  499.553474] 00000050: 00 00 00 02 00 00 00 00 00 00 00 00 7f 8a 1f c2  ................
[  499.557119] 00000060: ff ff ff ff fa c0 e6 7b 00 00 00 00 00 00 00 2a  .......{.......*
[  499.560735] 00000070: 00 00 16 c2 00 01 46 5a 00 00 00 00 00 00 00 00  ......FZ........
[  499.752447] XFS (nvme0n1p1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x5d1948 dinode
[  499.756148] XFS (nvme0n1p1): Unmount and run xfs_repair
[  499.759710] XFS (nvme0n1p1): First 128 bytes of corrupted metadata buffer:
[  499.763272] 00000000: 49 4e 81 ed 03 02 00 00 00 00 00 63 00 00 00 64  IN.........c...d
[  499.766895] 00000010: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  499.770498] 00000020: 66 16 cc 9c 0e c6 a0 a9 66 16 cc 9c 0e e5 25 4b  f.......f.....%K
[  499.774107] 00000030: 66 43 1b b8 18 8d a5 60 00 00 00 00 00 03 8e a0  fC.....`........
[  499.777695] 00000040: 00 00 00 00 00 00 00 39 00 00 00 00 00 00 00 01  .......9........
[  499.781243] 00000050: 00 00 00 02 00 00 00 00 00 00 00 00 7f 8a 1f c2  ................
[  499.784709] 00000060: ff ff ff ff fa c0 e6 7b 00 00 00 00 00 00 00 2a  .......{.......*
[  499.788173] 00000070: 00 00 16 c2 00 01 46 5a 00 00 00 00 00 00 00 00  ......FZ........

 

Looked scary, but easy to google, so I found some existing threads and the official docs. I took my array offline, started it again in Maintenance mode, and then ran xfs_repair (in the GUI after removing -n, and on commandline)

 

    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
            - process newly discovered inodes...
    Phase 4 - check for duplicate blocks...
            - setting up duplicate extent list...
            - check for inodes claiming duplicate blocks...
            - agno = 1
            - agno = 2
            - agno = 0
            - agno = 3
    Phase 5 - rebuild AG headers and trees...
            - reset superblock...
    Phase 6 - check inode connectivity...
            - resetting contents of realtime bitmap and summary inodes
            - traversing filesystem ...
            - traversal finished ...
            - moving disconnected inodes to lost+found ...
    Phase 7 - verify and correct link counts...
    done

Nothing reportedly found, nor fixed. But every time I run "dmesg" I get the same error. I'm not sure if it's a dmesg thing showing old data? Or if xfs_repair isn't finding my issue?

I have not yet tried xfs_repair with the -L flag, as my system seems to be running ok and I'd rather not blow stuff up and that command sounds scary to run on a whim.

 

Any advice on what needs to be done, if anything?

 

Edited May 14 by Chunks

[JorgeB]

The filesystem should be fixed now, reboot to clear the logs.

 

Don't recommend using -L unless xfs_repair asks for it.