downloadski Posted December 14, 2012 Share Posted December 14, 2012 I have started using cache directorys and during a mover run i had a crash it seems. The cause seems to be shortage of low memory if i read it correctly. Dec 14 18:51:35 Tower2 logger: >f+++++++++ movies/JAWS/BDMV/STREAM/50309.m2ts Dec 14 18:58:36 Tower2 kernel: rsync invoked oom-killer: gfp_mask=0x44d0, order=1, oom_adj=0, oom_score_a dj=0 Dec 14 18:58:36 Tower2 kernel: Pid: 23528, comm: rsync Not tainted 3.4.11-unRAID #1 Dec 14 18:58:36 Tower2 kernel: Call Trace: Dec 14 18:58:36 Tower2 kernel: [<c1060532>] T.619+0x56/0x159 Dec 14 18:58:36 Tower2 kernel: [<c1060f20>] ? zone_watermark_ok+0x1e/0x25 Dec 14 18:58:36 Tower2 kernel: [<c11a61ab>] ? ___ratelimit+0xaf/0xc4 Dec 14 18:58:36 Tower2 kernel: [<c106067a>] T.618+0x45/0x217 Dec 14 18:58:36 Tower2 kernel: [<c1029609>] ? has_ns_capability_noaudit+0x10/0x18 Dec 14 18:58:36 Tower2 kernel: [<c1029620>] ? has_capability_noaudit+0xf/0x11 Dec 14 18:58:36 Tower2 kernel: [<c1060a68>] out_of_memory+0x21c/0x29e Dec 14 18:58:36 Tower2 kernel: [<c10636bd>] __alloc_pages_nodemask+0x40b/0x4a5 Dec 14 18:58:36 Tower2 kernel: [<c1081b1e>] allocate_slab+0x5a/0xbc Dec 14 18:58:36 Tower2 kernel: [<c1081ba2>] new_slab+0x22/0xeb Dec 14 18:58:36 Tower2 kernel: [<c10820db>] T.1697+0x170/0x231 Dec 14 18:58:36 Tower2 kernel: [<c103ff73>] ? enqueue_task_fair+0x11a/0x132 Dec 14 18:58:36 Tower2 kernel: [<c129c7e2>] ? sock_alloc_send_pskb+0xc5/0x26b Dec 14 18:58:36 Tower2 kernel: [<c103b142>] ? check_preempt_curr+0x39/0x64 Dec 14 18:58:36 Tower2 kernel: [<c103b17c>] ? ttwu_do_wakeup+0xf/0xaa Dec 14 18:58:36 Tower2 kernel: [<c108325e>] __kmalloc_track_caller+0xa4/0xf2 Dec 14 18:58:36 Tower2 kernel: [<c129c7e2>] ? sock_alloc_send_pskb+0xc5/0x26b Dec 14 18:58:36 Tower2 kernel: [<c108325e>] ? __kmalloc_track_caller+0xa4/0xf2 Dec 14 18:58:36 Tower2 kernel: [<c129c7e2>] ? sock_alloc_send_pskb+0xc5/0x26b Dec 14 18:58:36 Tower2 kernel: [<c12a082d>] __alloc_skb+0x50/0xf5 Dec 14 18:58:36 Tower2 kernel: [<c129c7e2>] sock_alloc_send_pskb+0xc5/0x26b Dec 14 18:58:36 Tower2 kernel: [<c103b324>] ? __wake_up_sync_key+0x3c/0x45 Dec 14 18:58:36 Tower2 kernel: [<c129c996>] sock_alloc_send_skb+0xe/0x10 Dec 14 18:58:36 Tower2 kernel: [<c12f74ca>] unix_stream_sendmsg+0x12f/0x34d Dec 14 18:58:36 Tower2 kernel: [<c12993a3>] sock_aio_write+0xf1/0xfa Dec 14 18:58:36 Tower2 kernel: [<c1084996>] do_sync_write+0x94/0xcf Dec 14 18:58:36 Tower2 kernel: [<c10451eb>] ? ktime_get_ts+0xb9/0xc3 Dec 14 18:58:36 Tower2 kernel: [<c10851e2>] vfs_write+0x9a/0xfc Dec 14 18:58:36 Tower2 kernel: [<c10852db>] sys_write+0x3b/0x60 Dec 14 18:58:36 Tower2 kernel: [<c131fbb5>] syscall_call+0x7/0xb Dec 14 18:58:36 Tower2 kernel: [<c1310000>] ? alloc_node_mem_map+0x70/0x8a Dec 14 18:58:36 Tower2 kernel: Mem-Info: Dec 14 18:58:36 Tower2 kernel: DMA per-cpu: Dec 14 18:58:36 Tower2 kernel: CPU 0: hi: 0, btch: 1 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 1: hi: 0, btch: 1 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 2: hi: 0, btch: 1 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 3: hi: 0, btch: 1 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 4: hi: 0, btch: 1 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 5: hi: 0, btch: 1 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 6: hi: 0, btch: 1 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 7: hi: 0, btch: 1 usd: 0 Dec 14 18:58:36 Tower2 kernel: Normal per-cpu: Dec 14 18:58:36 Tower2 kernel: CPU 0: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 1: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 2: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 3: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 4: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 5: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 6: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 7: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: HighMem per-cpu: Dec 14 18:58:36 Tower2 kernel: CPU 0: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 1: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 2: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 3: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 4: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 5: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 6: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: CPU 7: hi: 186, btch: 31 usd: 0 Dec 14 18:58:36 Tower2 kernel: active_anon:2602 inactive_anon:39 isolated_anon:0 Dec 14 18:58:36 Tower2 kernel: active_file:40417 inactive_file:3800606 isolated_file:0 Dec 14 18:58:36 Tower2 kernel: unevictable:61736 dirty:614735 writeback:952 unstable:0 Dec 14 18:58:36 Tower2 kernel: free:50215 slab_reclaimable:33128 slab_unreclaimable:13596 Dec 14 18:58:36 Tower2 kernel: mapped:1776 shmem:68 pagetables:161 bounce:0 Dec 14 18:58:36 Tower2 kernel: DMA free:3532kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon: 0kB active_file:296kB inactive_file:248kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1 5796kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:7740kB slab_unreclaimabl e:4052kB kernel_stack:32kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:892 all _unreclaimable? yes Dec 14 18:58:36 Tower2 kernel: lowmem_reserve[]: 0 867 16114 16114 Dec 14 18:58:36 Tower2 kernel: Normal free:55288kB min:3732kB low:4664kB high:5596kB active_anon:0kB inac tive_anon:0kB active_file:22236kB inactive_file:22380kB unevictable:0kB isolated(anon):0kB isolated(file) :0kB present:887960kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:124772kB slab_unreclaimable:50332kB kernel_stack:1120kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB p ages_scanned:86194 all_unreclaimable? yes Dec 14 18:58:36 Tower2 kernel: lowmem_reserve[]: 0 0 121978 121978 Dec 14 18:58:36 Tower2 kernel: HighMem free:142040kB min:512kB low:16924kB high:33336kB active_anon:10408 kB inactive_anon:156kB active_file:139136kB inactive_file:15179796kB unevictable:246944kB isolated(anon): 0kB isolated(file):0kB present:15613304kB mlocked:0kB dirty:2458940kB writeback:3808kB mapped:7100kB shme m:272kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:644kB unstable:0kB bounce :0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Dec 14 18:58:36 Tower2 kernel: lowmem_reserve[]: 0 0 0 0 Dec 14 18:58:36 Tower2 kernel: DMA: 117*4kB 293*8kB 9*16kB 2*32kB 0*64kB 2*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3532kB Dec 14 18:58:36 Tower2 kernel: Normal: 13377*4kB 107*8kB 28*16kB 3*32kB 0*64kB 0*128kB 0*256kB 1*512kB 0* 1024kB 0*2048kB 0*4096kB = 55420kB Dec 14 18:58:36 Tower2 kernel: HighMem: 7*4kB 6*8kB 9*16kB 7*32kB 3*64kB 2*128kB 552*256kB 0*512kB 0*1024 kB 0*2048kB 0*4096kB = 142204kB Dec 14 18:58:36 Tower2 kernel: 3902927 total pagecache pages Dec 14 18:58:36 Tower2 kernel: 0 pages in swap cache Dec 14 18:58:36 Tower2 kernel: Swap cache stats: add 0, delete 0, find 0/0 Dec 14 18:58:36 Tower2 kernel: Free swap = 0kB Dec 14 18:58:36 Tower2 kernel: Total swap = 0kB Should i terminate cache dirs before i run the mover ? Why all these issues with low memory ? Is that the problem with 32 bit OS ? Why is there not an 64 bit version, all hardware since at least 2 years is 64 bit capable i think ? Link to comment
Joe L. Posted December 14, 2012 Share Posted December 14, 2012 stopping cache_dirs probably will not help, since it is coded to suspend itself when the "mover" script is running. That change was added a long time ago to prevent duplicate-file messages as the mover copied files to the protected array. # Version 1.6.4 - Modified to suspend scan during time "mover" script is running to prevent # DuplicateFile messages from occurring as file is being copied. # - Added -S option to NOT suspend scan during mover process. So, unless you invoked it with the -S option, odds are you just ran out of "low memory" You can certainly try once more after killing it, but you'll probably need to empty the disk cache buffers to reclaim the low memory needed. Joe L. Link to comment
downloadski Posted December 14, 2012 Author Share Posted December 14, 2012 I also changed the "adjustable parameters" to 5x original value. I now changed them back to original settings. Perhaps that was the issue. Today i did copy also 250 gb to the protected volume withouth the cache drive, and that worked without any issues. Perhaps the mover process needs more memory than a copy over the lan ? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.