>If I look in /var/log/messages on my client machine, I see this:
>{{{
>Oct 20 21:00:48 andLinux -- MARK --
>Oct 20 21:20:48 andLinux -- MARK --
>Oct 20 21:40:48 andLinux -- MARK --
>Oct 20 22:00:49 andLinux -- MARK --
>Oct 20 22:21:09 andLinux -- MARK --
>Oct 20 22:41:37 andLinux -- MARK --
>Oct 20 22:43:23 andLinux kernel: kded4 invoked oom-killer:
>gfp_mask=0x201d2, order=0, oomkilladj=0
>Oct 20 22:43:23 andLinux kernel: dd invoked oom-killer: gfp_mask=0x200d2,
>order=0, oomkilladj=0
>Oct 20 22:43:23 andLinux kernel:  [<c0103b7a>] show_trace_log_lvl+0x1a/0x30
>Oct 20 22:43:23 andLinux kernel:  [<c0103cb2>] show_trace+0x12/0x20
>Oct 20 22:43:23 andLinux kernel:  [<c0104ae5>] dump_stack+0x15/0x20
>Oct 20 22:43:23 andLinux kernel:  [<c014197d>] out_of_memory+0x19d/0x200
>Oct 20 22:43:23 andLinux kernel:  [<c014319a>] __alloc_pages+0x2da/0x330
>Oct 20 22:43:23 andLinux kernel:  [<c0152b11>]
>read_swap_cache_async+0xa1/0xe0
>Oct 20 22:43:23 andLinux kernel:  [<c01492f5>] swapin_readahead+0x55/0x70
>Oct 20 22:43:23 andLinux kernel:  [<c014b98e>]
>__handle_mm_fault+0x82e/0xa00
>Oct 20 22:43:23 andLinux kernel:  [<c010b541>] do_page_fault+0x351/0x690
>Oct 20 22:43:23 andLinux kernel:  [<c02e81fa>] error_code+0x6a/0x70
>Oct 20 22:43:23 andLinux kernel:  [<c019d315>] kmsg_read+0x25/0x50
>Oct 20 22:43:23 andLinux kernel:  [<c015e105>] vfs_read+0xb5/0x140
>Oct 20 22:43:23 andLinux kernel:  [<c015e4ed>] sys_read+0x3d/0x70
>Oct 20 22:43:23 andLinux kernel:  [<c01028f2>] syscall_call+0x7/0xb
>Oct 20 22:43:23 andLinux kernel:  =======================
>Oct 20 22:43:23 andLinux kernel: Mem-info:
>Oct 20 22:43:23 andLinux kernel: Normal per-cpu:
>Oct 20 22:43:23 andLinux kernel: CPU    0: Hot: hi:   90, btch:  15 usd:  
>5   Cold: hi:   30, btch:   7 usd:   6
>Oct 20 22:43:23 andLinux kernel: Active:30295 inactive:30529 dirty:0
>writeback:0 unstable:0
>Oct 20 22:43:23 andLinux kernel:  free:509 slab:1850 mapped:42
>pagetables:315 bounce:0
>Oct 20 22:43:23 andLinux kernel: Normal free:2036kB min:2036kB low:2544kB 
>high:3052kB active:121180kB inactive:122116kB present:260096kB 

Is this a virtual machine? 260096kB of RAM was probably not enough.
Therefore it used a lot of swap memory, which explains why the process took
so long.

>pages_scanned:407510 all_unreclaimable? yes
>Oct 20 22:43:23 andLinux kernel: lowmem_reserve[]: 0
>Oct 20 22:43:23 andLinux kernel: Normal: 11*4kB 3*8kB 1*16kB 1*32kB 0*64kB
>1*128kB 1*256kB 1*512kB 1*1024kB 0*2048kB 0*4096kB = 2036kB
>Oct 20 22:43:23 andLinux kernel: Swap cache: add 1043236, delete 1043236,
>find 25790/146554, race 0+0
>Oct 20 22:43:23 andLinux kernel: Free swap  = 0kB

*ouch* Looks like you've had no swap left, either. Probably you ran out of
memory during the commit and the process was killed by the kernel when the
process tried to allocate even more.

Cheers

Reply via email to