Bug 26540 - Errors: Structure needs cleaning
Summary: Errors: Structure needs cleaning
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-25 20:30 CEST by Stig-Ørjan Smelror
Modified: 2020-04-25 21:10 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Stig-Ørjan Smelror 2020-04-25 20:30:14 CEST
I've just installed kernel 5.6.7-3, latest systemd 245.5, updated glibc and grub2 and am getting a strange message that I've never seen before.

% /bin/ls -l /usr/bin | more
/bin/ls: cannot access '/usr/bin/build-classpath': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/build-classpath-directory': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/build-jar-repository': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/check-binary-files': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/clean-binary-files': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/create-jar-links': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/diff-jars': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/find-jar': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/rebuild-jar-repository': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/shade-jar': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/git': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/git-shell': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/git-receive-pack': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/git-upload-archive': Structure needs cleaning
/bin/ls: cannot access '/usr/bin/git-upload-pack': Structure needs cleaning

It also shows up when I'm root.

Wanted to try xfs_repair and since I don't know what I'm doing, this is what I got.

[root@dellirium ~]# xfs_repair /dev/sda1
xfs_repair: /dev/sda1 contains a mounted filesystem
xfs_repair: /dev/sda1 contains a mounted and writable filesystem

fatal error -- couldn't initialize XFS library

[root@dellirium ~]# mount | grep sda
/dev/sda1 on / type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
/dev/sda6 on /home type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)

% sudo journalctl -xe
Apr 25 20:25:48 dellirium kernel: XFS (sda1): Metadata corruption detected at xfs_buf_ioend+0x56/0x1c0 [xfs], xfs_inode block 0x19680 xfs_inode_buf_verify
Apr 25 20:25:48 dellirium kernel: XFS (sda1): Unmount and run xfs_repair
Apr 25 20:25:48 dellirium kernel: XFS (sda1): First 128 bytes of corrupted metadata buffer:
Apr 25 20:25:48 dellirium kernel: 00000000: 8a 9a 56 61 4a 47 b9 90 97 22 7d 59 af b5 b6 bf  ..VaJG..."}Y....
Apr 25 20:25:48 dellirium kernel: 00000010: 3b ac f0 e8 2e 53 f4 da 26 de 9e c4 03 44 93 5b  ;....S..&....D.[
Apr 25 20:25:48 dellirium kernel: 00000020: 73 b9 87 28 af f3 e4 2a 5a bf d2 15 4e 1e f2 47  s..(...*Z...N..G
Apr 25 20:25:48 dellirium kernel: 00000030: a3 bd a1 8d c9 0c a4 1a c5 5f d4 c0 9f 5d 1a 0e  ........._...]..
Apr 25 20:25:48 dellirium kernel: 00000040: 20 44 3f 26 7b d4 86 fb 14 58 77 46 92 f7 3b 33   D?&{....XwF..;3
Apr 25 20:25:48 dellirium kernel: 00000050: 15 87 aa 12 7a 4d 0d 9f 33 42 e1 8c c2 f5 96 fd  ....zM..3B......
Apr 25 20:25:48 dellirium kernel: 00000060: 55 6c cd d0 58 e2 6d 4f 6d e2 62 db ed b9 3a 96  Ul..X.mOm.b...:.
Apr 25 20:25:48 dellirium kernel: 00000070: 11 59 b5 d6 25 d5 ce ce bb a6 d0 d7 46 2f 4c 22  .Y..%.......F/L"
Apr 25 20:25:48 dellirium kernel: XFS (sda1): metadata I/O error in "xfs_iread+0x9c/0x210 [xfs]" at daddr 0x19680 len 32 error 117
Apr 25 20:25:48 dellirium kernel: XFS (sda1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.

Will reboot using a USB stick and try xfs_repair.
Comment 1 Stig-Ørjan Smelror 2020-04-25 21:10:39 CEST
A quick boot from a USB stick and running xfs_repair cleared the messages.

I really need a new(er) computer!

Cheers,
Stig

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.