https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #184 from Lei Ming (tom.leiming@xxxxxxxxx) --- The commit 2a5cf35cd6c56b2924("block: fix single range discard merge") in linus tree may address one possible data loss, anyone who saw corruption in scsi may try this fix and see if it makes a difference. Given the merged discard request isn't removed from elevator queue, it might be possible to be submitted to hardware again.(In reply to Theodore Tso from comment #174) > One of the reasons why this is bug hunt is so confounding. While I was > looking at older reports to try to see if I could find common factors, I > found Jimmy's dmesg report in #50, and this one looks different from many of > the others that people have reported. In this one, the EXT4 errors are > preceeded by a USB disconnect followed by disk-level errors. > > This is why it's important that we try very hard to filter out false > positives and false negative reports. We have multiple reports which both > strongly indicate that it's an ext4 bug, and others which strongly indicate > it is a bug below the file system layer. And then we have ones like this > which look like a USB disconnect.... > > [52967.931390] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using > xhci_hcd IMO it should be a usb device reset instead of disconnect, and reset is often triggered in SCSI EH. Thanks, -- You are receiving this mail because: You are watching the assignee of the bug.
