Messages in this thread |  | | | Date | Wed, 23 Feb 2000 14:07:14 +0100 (CET) | | From | André Dahlqvist <> | | Subject | Re: 2.3.47: elevator nr_segments x should be x+1 |
| |
>>I can reliably reproduce this by either compiling a kernel or >>uudecoding a large file in one virtual console while reading mail/news >>in another VT. > >03 major number too?
I don't know if it is of any help to you, but I have also seen messages like these quiet regularly during the last couple of days.
Below are those I found in my logs. The ones marked with (*) happened when the "updatedb" cron job runs, which of course causes heavy disk activity.
Feb 17 14:06:25 __elevator_merge: req latency 54 req latency 53 (*) Feb 18 07:36:45 03:02: elevator nr_segments 86 should be 87 Feb 19 16:30:20 __elevator_merge: req latency 54 req latency 53 Feb 19 16:34:58 __elevator_merge: req latency 54 req latency 53 Feb 19 17:24:21 __elevator_merge: req latency 54 req latency 53 Feb 19 18:12:31 __elevator_merge: req latency 54 req latency 53 Feb 19 18:41:59 __elevator_merge: req latency 54 req latency 53 Feb 20 00:53:19 03:03: elevator nr_segments 134 should be 135 Feb 20 16:22:35 __elevator_merge: req latency 54 req latency 53 (*) Feb 21 07:36:55 03:02: elevator nr_segments 250 should be 251 (*) Feb 22 07:36:35 03:02: elevator nr_segments 162 should be 163
// André
=================================================================== André Dahlqvist <andre@beta.telenordia.se> GnuPG Key ID: 0x70A2994A Fingerprint: E947 3297 331C CA30 5B88 EDF2 A830 3EBE 70A2 994A ===================================================================
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
|  |