On Sonntag 05 September 2004 18:49, Jari Ruusu wrote: > David Gümbel wrote: > > I applied the patch and tested it. The error remains there - both the > > "ls /tmp" (encrypted reiserfs) error and the "ls > > ~/Mail/Spamverdacht/new/" (encrypted ext3) error. > > > > These are dmesg lines starting with "loop" after trying the /tmp error: > > > > guembel@marsupilami v4 $ cat dmesg_tmp_input_output_error.txt | grep > > ^loop loop: loaded (max 8 devices) > > loop1: loop_end_io_transfer err=-11 bi_rw=0x2 > > loop1: loop_end_io_transfer err=-11 bi_rw=0x2 > > loop1: loop_end_io_transfer err=-11 bi_rw=0x2 > Above means that underlying device I/O elevator (hda), failed read-ahead > requests (bi_rw=0x2) with -EWOULDBLOCK error code (err=-11, uses same > error code as -EAGAIN). I/O elevator treats read-ahead requests little > bit more relaxed than normal read or write requests. It has liberty to > fail them in case of congestion or free memory pressure. Loop driver > reported underlying device error to file system on top of loop device. > File system should have ignored failed read-ahead requests, but it > didn't, so you saw I/O errors as result. Same situation can happen on > unencrypted file systems that do not go through loop device. It is a > kernel bug. OK, that sounds good. One question, though: How come that this error happens on encrypted loop device (obviously) more often than on unencrypted filesystems, and why can it be triggered so predictively in my ~/Mail/Spamverdacht/new case? > Can you test attached patch? It transforms read-ahead requests from file > system to normal reads for underlying device. Normal read requests should > not fail with -EWOULDBLOCK so this should cure the problem. Just applied it, will test with 2.6.8.1 ASAP. Thanks again for your efforts, David -- David Gümbel . . . . . . . . . . . . . . . . david.guembel@xxxxxxxxx ITOMIG GbR . . . . . . . . . . . . . . . . . phone: +49 7071 2970493 Sand 14 . . . . . . . . . . . . . . . . . . mobil: +49 179 5400885 D-72076 Tübingen . . . . . . . . . . . . . . . .http://www.itomig.de
Attachment:
pgpOWQTDQOPAD.pgp
Description: PGP signature
