XFS (dm-0) Internal error XFS_WANT_CORRUPTED

[linux_guy]

today my server is acting up, and it's not working, Im not sure how to fix it, here is the error i am getting:

[29.334924] XFS (dm-0): Internal error XFS_WANT_CORRUPTED_GOTO at line 1337 of file fs/xfs/libxfs/xfs_ialloc.c. Caller xfs_dialloc_ag+0x6e/0x290 [xfs]


does anyone know what's going on?

help!

[linux_guy]

this morning, my other centos machine is also not even able to boot, here is what happens,

centos.png (15.16 KiB) Viewed 16223 times

i did a memtest throughout the night and there isnt any problem with the memory

results below:

https://imgur.com/a/3SZCcl5


not sure what to do,

it's both centos server virtual machines, they are virtual machine on my servers,

i have 4 virtual machines on my server, 2 centos and 2 windows, the windows ones are working fine,

its just my centos machine

they are running centos 7.6. 1810


any idea?

[TrevorH]

Boot the install media in rescue mode and try xfs_repair.

[linux_guy]

thank you! that fixed it,

i booted into rescue mode:

1. During bootup, when the GRUB2 menu shows up, press the e key for edit

2. Add the following parameter at the end of the linux16 line, after quiet:

quiet systemd.unit=emergency.target


3. Press Ctrl+x to boot the system with the parameter.

4. first find your device UUID in /dev/disk/by-uuid

5. umount

umount /dev/disk/by-uuid/198s5364-a29c-429e-b16d-e772acd

6 repair

xfs_repair /dev/disk/by-uuid/198s5364-a29c-429e-b16d-e772acd


then i rebooted, and the errors went away,

why exactly did that happen?

thanks for the help



edit:
sometimes you have to force it by deleting the log file

xfs_repair -L /dev/disk/by-uuid/198s5364-a29c-429e-b16d-e772acd

[desertcat]

thank you! that fixed it,

i booted into rescue mode:

1. During bootup, when the GRUB2 menu shows up, press the e key for edit

2. Add the following parameter at the end of the linux16 line, after quiet:

quiet systemd.unit=emergency.target


3. Press Ctrl+x to boot the system with the parameter.

4. first find your device UUID in /dev/disk/by-uuid

5. umount

umount /dev/disk/by-uuid/198s5364-a29c-429e-b16d-e772acd

6 repair

xfs_repair /dev/disk/by-uuid/198s5364-a29c-429e-b16d-e772acd


then i rebooted, and the errors went away,

why exactly did that happen?

thanks for the help

I *suspect* you had a corrupted file or files. xfs_repair is *probably* similar to fsck that is used with ext2,3,4.
After running for years without any problems I had a HDD suddenly go out into the weeds. For reasons unknown. I mounted the drive under CentOS7 than ran fsck on /dev/sdc* where the *=the partition #. I ran fsck on EVERY partition and sure enough it found corrupted files and fixed them. Now the problem has gone away. _SHRUG_

[centbala]

I am glad that you able to root cause the problem and fix it. I am also observing the same problem with my VMs and looking for some additional help. I was wondering how did you find the uuid for multipath devices like dm-0 that was throwing XFS errors. Did you umount and xfs_repair the uuid of /dev/mapper/centos-root?

Thanks

[linux_guy]

you have to type:
/dev/disk/by-uuid

that will get you inside the uuid folder, then you have to type another command to show you all the uuid's, so then type:

ls

then it will show you all the uuid, i unmounted it first i believe, look in my first post

[echsec04]

Hi,
I followed the same steps but after reboot. there blank screen. Please help