https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #252 from Jens Axboe (axboe@xxxxxxxxx) --- (In reply to Guenter Roeck from comment #247) > #245: Is there a means to log the possible error case ? Yes, that's how I ended up verifying that this was indeed what was going on. Example: [ 235.665576] issue_direct=13, 22080, ffff9ee3da59e400 [ 235.931483] bio_attempt_back_merge: MERGE ON NO PREP ffff9ee3da59e400 [ 235.931486] bio_attempt_back_merge: MERGE ON NO PREP ffff9ee3da59e400 [ 235.931489] bio_attempt_back_merge: MERGE ON NO PREP ffff9ee3da59e400 [ 235.934465] EXT4-fs error (device sda1): ext4_iget:4831: inode #7142: comm dpkg-query: bad extra_isize 24937 (inode size 256) Here we see req 0xffff9ee3da59e400 being rejected, due to resource starvation. Shortly thereafter, we see us happily merging more IO into that request. Once that request finishes, ext4 gets immediately unhappy as only a small part of the request contents were valid. The rest simply contained garbage. -- You are receiving this mail because: You are watching the assignee of the bug.
