NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
btaroli
Jan 15, 2017Prodigy
6.6.1 Scrub Hammers CPU
And when I say hammers, I mean it runs with -1 prio and causes 6-8 kernel worker threads each vying to consume 100% of CPU. So rabid is this consumption that all other background processes, including...
btaroli
Jan 16, 2017Prodigy
Sure, I'd be glad to. This is on a 528.
Just for the sake of completeness, here's top with just background running...
top - 03:34:19 up 3 days, 49 min, 2 users, load average: 0.01, 0.03, 0.06 Tasks: 241 total, 2 running, 239 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.4 us, 0.7 sy, 0.0 ni, 98.8 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 16303964 total, 15086028 used, 1217936 free, 2468 buffers KiB Swap: 3139580 total, 0 used, 3139580 free. 13522476 cached Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 11971 root 20 0 3584900 356660 27084 S 4.0 2.2 182:46.02 /apps/dvblink-tv-server/dvblink_server 10318 root 20 0 233308 31464 5660 S 1.0 0.2 40:27.23 /usr/bin/python /apps/dropboxmanager/web/manage.py run+ 5138 root 20 0 992516 12028 8796 S 0.3 0.1 18:19.58 /opt/p2p/bin/leafp2p -n 5419 root 20 0 28788 3060 2468 R 0.3 0.0 7:33.54 top 22590 root 20 0 0 0 0 S 0.3 0.0 0:00.30 [kworker/2:6] 1 root 20 0 202460 6504 4516 S 0.0 0.0 0:38.41 /sbin/init 2 root 20 0 0 0 0 S 0.0 0.0 0:00.10 [kthreadd] 3 root 20 0 0 0 0 S 0.0 0.0 0:06.33 [ksoftirqd/0] 5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 [kworker/0:0H] 7 root 20 0 0 0 0 R 0.0 0.0 0:57.85 [rcu_sched] 8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [rcu_bh] 9 root rt 0 0 0 0 S 0.0 0.0 0:00.21 [migration/0] 10 root rt 0 0 0 0 S 0.0 0.0 0:00.83 [watchdog/0] 11 root rt 0 0 0 0 S 0.0 0.0 0:00.85 [watchdog/1] 12 root rt 0 0 0 0 S 0.0 0.0 0:00.24 [migration/1] 13 root 20 0 0 0 0 S 0.0 0.0 0:03.26 [ksoftirqd/1] 15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 [kworker/1:0H]
And here's what it looks like shortly after kicking off a scrub.
top - 03:34:19 up 3 days, 49 min, 2 users, load average: 0.01, 0.03, 0.06 Tasks: 241 total, 2 running, 239 sleeping, 0 stopped, 0 zombie top - 03:39:04 up 3 days, 53 min, 2 users, load average: 2.67, 0.65, 0.26 Tasks: 249 total, 7 running, 242 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.5 us, 95.1 sy, 0.0 ni, 3.5 id, 0.0 wa, 0.0 hi, 0.9 si, 0.0 st KiB Mem: 16303964 total, 15111680 used, 1192284 free, 2468 buffers KiB Swap: 3139580 total, 0 used, 3139580 free. 13537484 cached Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 14083 root 20 0 0 0 0 R 69.1 0.0 0:10.26 [kworker/u8:2] 18741 root 20 0 0 0 0 R 59.1 0.0 0:10.26 [kworker/u8:0] 22107 root 20 0 0 0 0 R 55.5 0.0 0:08.28 [kworker/u8:1] 23262 root 20 0 0 0 0 R 55.1 0.0 0:08.74 [kworker/u8:9] 23253 root 20 0 0 0 0 R 51.5 0.0 0:05.02 [kworker/u8:7] 9426 root 20 0 0 0 0 R 50.1 0.0 0:09.49 [kworker/u8:5] 2455 root 20 0 0 0 0 S 18.9 0.0 1:37.18 [md126_raid6] 23229 root 19 -1 40340 212 12 S 10.0 0.0 0:02.30 btrfs scrub start /data 18976 root 20 0 0 0 0 S 4.3 0.0 0:02.26 [kworker/u8:8] 11971 root 20 0 3584900 356660 27084 S 3.7 2.2 182:56.16 /apps/dvblink-tv-server/dvblink_server 5335 root 19 -1 1589984 59196 12228 S 2.0 0.4 5:41.17 /usr/sbin/readynasd -v 3 -t 10318 root 20 0 233308 31464 5660 S 1.7 0.2 40:29.84 /usr/bin/python /apps/dropboxmanager/web/manage.py run+ 23226 root 39 19 0 0 0 D 1.3 0.0 0:00.35 [md126_resync] 2335 root 0 -20 0 0 0 S 0.7 0.0 0:01.65 [kworker/1:1H] 5138 root 20 0 992516 12028 8796 S 0.7 0.1 18:20.82 /opt/p2p/bin/leafp2p -n 22590 root 20 0 0 0 0 S 0.7 0.0 0:01.27 [kworker/2:6] 2340 root 0 -20 0 0 0 S 0.3 0.0 0:27.69 [kworker/0:1H]
FramerV
Jan 17, 2017NETGEAR Employee Retired
Hi btaroli,
Have you sent your logs already?
I will be sending an inquiry to our subject matter expert about it if have you did.
Regards,
- btaroliJan 17, 2017Prodigy
Sent them attn to mdgm the same time I posted my reply.
- FramerVJan 18, 2017NETGEAR Employee Retired
Hi btaroli,
Okay, I will give mdgm a heads up about your case.
Regards,
- mdgm-ntgrFeb 23, 2017NETGEAR Employee Retired
There have been some changes in 6.7.0, I think. Do you still have this problem on ReadyNASOS 6.7.0-T158 (Beta 1)?
- btaroliFeb 23, 2017Prodigy
I'd certainly be willing to try it. Given some pain in the last upgrade or two, I've been a little shy to want to rush into betas. I'll take a look at the release notes and forums posts on this one and the give it a try if it's looking fairly quiet on the problem front.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!