| To: | Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2 |
| From: | Bill Cizek <cizek@xxxxxxx> |
| Date: | Wed, 24 Jan 2007 19:21:20 -0600 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, linux-raid@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.64.0701241909120.2930@p34.internal.lan> |
| References: | <Pine.LNX.4.64.0701211424170.2552@p34.internal.lan> <20070122115703.97ed54f3.akpm@osdl.org> <Pine.LNX.4.64.0701241909120.2930@p34.internal.lan> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 1.5.0.9 (X11/20061206) |
Justin Piszcz wrote:
On Mon, 22 Jan 2007, Andrew Morton wrote: Justin, According to your kernel_ring_buffer.txt (attached to another email), you are using "anticipatory" as your io scheduler: 289 Jan 24 18:35:25 p34 kernel: [ 0.142130] io scheduler noop registered 290 Jan 24 18:35:25 p34 kernel: [ 0.142194] io scheduler anticipatory registered (default) I had a problem with this scheduler where my system would occasionally lockup during heavy I/O. Sometimes it would fix itself, sometimes I had to reboot. I changed to the "CFQ" io scheduler and my system has worked fine since then. CFQ has to be built into the kernel (under BlockLayer/IOSchedulers). It can be selected as default or you can set it during runtime: echo cfq > /sys/block/<disk>/queue/scheduler ... Hope this helps, Bill |
| Previous by Date: | Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2, Justin Piszcz |
|---|---|
| Next by Date: | Re: [PATCH 1/2]: Fix BUG in cancel_dirty_pages on XFS, David Chinner |
| Previous by Thread: | Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2, Justin Piszcz |
| Next by Thread: | Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2, Justin Piszcz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |