Bug 24907 - fs corruption with kernel 5.1.6 ?
Summary: fs corruption with kernel 5.1.6 ?
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-05 09:51 CEST by José Jorge
Modified: 2019-08-02 15:25 CEST (History)
1 user (show)

See Also:
Source RPM: kernel-desktop586-5.1.6
CVE:
Status comment:


Attachments
dmesg showing a kernel bug (63.03 KB, text/plain)
2019-06-05 09:53 CEST, José Jorge
Details

Description José Jorge 2019-06-05 09:51:06 CEST
As reported on dev ML, I am experiencing file "strange" filesystem errors since kernel 5.1.6.

For now, I am not 100% sure this is not an hardware problem as it only happens in one system. It is a 2009 Asus EeePC with 2 SSD disks.

This report is here for further investigation.
Comment 1 José Jorge 2019-06-05 09:53:13 CEST
Created attachment 11062 [details]
dmesg showing a kernel bug

It also shows an error in one /dev/sdb sector, while a full read of the SSD disks shows no problem...
Comment 2 Dave Hodgins 2019-06-11 00:31:03 CEST
The important lines from that attachment appear to be ...
[  636.459610] sd 1:0:1:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[  636.459626] sd 1:0:1:0: [sdb] tag#0 CDB: Test Unit Ready 
[  636.459633] print_req_error: I/O error, dev sdb, sector 10460616 flags 80700

It could be a faulty drive, cable (dirty or loose connections, broken wire that
sometimes connects), or a fault in the drive controller.
Whichever one it is, it looks like a hardware failure, not a software problem.

CC: (none) => davidwhodgins

Comment 3 Dave Hodgins 2019-06-11 00:32:46 CEST
I should have added, that it can appear to only affect the one kernel, as that
kernel is using files written into a bad block within the ssd drive.
Comment 4 José Jorge 2019-08-02 15:25:16 CEST
Closing as it did not happen again...

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


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