学院 › 黑白群晖 › kworker进程导致黑群不能硬盘休眠，请问是什么原因？

wus6008 发表于 2019-12-9 14:11:44

kworker进程导致黑群不能硬盘休眠，请问是什么原因？

无事折腾，重装黑群。在没有安装任何套件的情况下，简单设置可实现黑群硬盘休眠后自动关机，并搭配路由padavan固件的局域网唤醒实现WOL。
但是在不自动关机前提下，持续通电开机，经过两三天的日志记录和日志分析，发现黑群硬盘会不定时被唤醒，间隔时间不定。
遍寻无果，对比几个未得到答案的帖子以及剔除个别因素，最终判断影响个人黑群的原因为Kworker这个进程。
如有大神了解原因，请指教，感谢。

以下为相关记录说明。

（1）黑群版本 DS3617xs，版本:DSM 6.2-23739


（2）硬盘休眠设置


（3）唤醒日志


（4）hibernationFull.log（已经剔除synologrotated、logrotate、dirtied inode、on tmpfs、on proc等无关行）
         比对以上唤醒日志，经过分析hibernationFull日志文件后得出影响因素为kworker不定时read硬盘第一个分区


求解：原因及处理办法

#####################################################
***********Clear*********
kworker/1:2(2378): READ block 4980352 on sda1 (8 sectors)
kworker/1:2(2378): READ block 4980352 on sdb1 (8 sectors)
kworker/1:2(2378): READ block 4980352 on sda1 (8 sectors)
kworker/1:2(2378): READ block 4980352 on sdb1 (8 sectors)
uptime :
======Idle 2090 seconds======
Mon Dec 9 00:07:52 CST 2019
#####################################################
***********Clear*********
kworker/1:2(2378): READ block 4980352 on sda1 (8 sectors)
kworker/1:2(2378): READ block 4980352 on sdb1 (8 sectors)
uptime :
======Idle 23 seconds======
Mon Dec 9 00:08:16 CST 2019
#####################################################
***********Clear*********
kworker/1:2(2378): READ block 4980352 on sda1 (8 sectors)
kworker/1:2(2378): READ block 4980352 on sdb1 (8 sectors)
kworker/2:1(6384): READ block 4980352 on sda1 (8 sectors)
kworker/2:1(6384): READ block 4980352 on sdb1 (8 sectors)
uptime :
======Idle 838 seconds======
Mon Dec 9 00:22:16 CST 2019
#####################################################
***********Clear*********
kworker/1:2(2378): READ block 4980352 on sda1 (8 sectors)
kworker/1:2(2378): READ block 4980352 on sdb1 (8 sectors)
kworker/2:1(6384): READ block 4980352 on sda1 (8 sectors)
kworker/2:1(6384): READ block 4980352 on sdb1 (8 sectors)
uptime :
======Idle 23 seconds======
Mon Dec 9 00:22:40 CST 2019
#####################################################
***********Clear*********
kworker/2:1(6384): READ block 4980352 on sda1 (8 sectors)
kworker/2:1(6384): READ block 4980352 on sdb1 (8 sectors)
uptime :
======Idle 23 seconds======
Mon Dec 9 00:23:04 CST 2019
#####################################################
***********Clear*********
kworker/2:1(6384): READ block 4980352 on sda1 (8 sectors)
kworker/2:1(6384): READ block 4980352 on sdb1 (8 sectors)
kworker/0:2(13892): READ block 4980352 on sda1 (8 sectors)
kworker/0:2(13892): READ block 4980352 on sdb1 (8 sectors)
kworker/1:2(2378): READ block 8 on sda3 (8 sectors)
kworker/1:2(2378): READ block 8 on sdb3 (8 sectors)
uptime :
======Idle 12298 seconds======
Mon Dec 9 03:48:04 CST 2019
#####################################################
***********Clear*********
kworker/0:2(13892): READ block 4980352 on sda1 (8 sectors)
kworker/0:2(13892): READ block 4980352 on sdb1 (8 sectors)
kworker/1:2(2378): READ block 8 on sda3 (8 sectors)
kworker/1:2(2378): READ block 8 on sdb3 (8 sectors)
uptime :
======Idle 23 seconds======
Mon Dec 9 03:48:28 CST 2019
#####################################################
***********Clear*********
kworker/0:2(13892): READ block 4980352 on sda1 (8 sectors)
kworker/0:2(13892): READ block 4980352 on sdb1 (8 sectors)
kworker/1:2(2378): READ block 8 on sda3 (8 sectors)
kworker/1:2(2378): READ block 8 on sdb3 (8 sectors)
kworker/0:2(13892): READ block 4980352 on sda1 (8 sectors)
kworker/0:2(13892): READ block 4980352 on sdb1 (8 sectors)
kworker/1:2(2378): READ block 8 on sda3 (8 sectors)
kworker/3:2(6792): READ block 8 on sdb3 (8 sectors)
uptime :
======Idle 3188 seconds======
Mon Dec 9 04:41:37 CST 2019
#####################################################
***********Clear*********
kworker/0:2(13892): READ block 4980352 on sda1 (8 sectors)
kworker/0:2(13892): READ block 4980352 on sdb1 (8 sectors)
kworker/1:2(2378): READ block 8 on sda3 (8 sectors)
kworker/3:2(6792): READ block 8 on sdb3 (8 sectors)
uptime :
======Idle 27 seconds======
Mon Dec 9 04:42:05 CST 2019
#####################################################
***********Clear*********
kworker/0:2(13892): READ block 4980352 on sda1 (8 sectors)
kworker/0:2(13892): READ block 4980352 on sdb1 (8 sectors)
kworker/1:2(2378): READ block 8 on sda3 (8 sectors)
kworker/3:2(6792): READ block 8 on sdb3 (8 sectors)
uptime :
======Idle 35 seconds======
Mon Dec 9 04:42:41 CST 2019
#####################################################
***********Clear*********
kworker/0:2(13892): READ block 4980352 on sda1 (8 sectors)
kworker/0:2(13892): READ block 4980352 on sdb1 (8 sectors)
kworker/1:2(2378): READ block 8 on sda3 (8 sectors)
kworker/3:2(6792): READ block 8 on sdb3 (8 sectors)
uptime :
======Idle 5113 seconds======
Mon Dec 9 06:07:56 CST 2019
#####################################################
***********Clear*********
kworker/1:2(2378): READ block 4980352 on sda1 (8 sectors)
kworker/1:2(2378): READ block 4980352 on sdb1 (8 sectors)
uptime :
======Idle 33 seconds======
Mon Dec 9 06:08:30 CST 2019
#####################################################
***********Clear*********
kworker/1:2(2378): READ block 4980352 on sda1 (8 sectors)
kworker/1:2(2378): READ block 4980352 on sdb1 (8 sectors)
kworker/2:0(31017): READ block 4980352 on sda1 (8 sectors)
kworker/2:0(31017): READ block 4980352 on sdb1 (8 sectors)
uptime :
======Idle 4231 seconds======
Mon Dec 9 07:19:03 CST 2019
#####################################################
***********Clear*********
kworker/1:2(2378): READ block 4980352 on sda1 (8 sectors)
kworker/1:2(2378): READ block 4980352 on sdb1 (8 sectors)
kworker/2:0(31017): READ block 4980352 on sda1 (8 sectors)
kworker/2:0(31017): READ block 4980352 on sdb1 (8 sectors)
uptime :
======Idle 25 seconds======
Mon Dec 9 07:19:30 CST 2019
#####################################################
***********Clear*********
kworker/2:0(31017): READ block 4980352 on sda1 (8 sectors)
kworker/2:0(31017): READ block 4980352 on sdb1 (8 sectors)
kworker/2:0(31017): READ block 4980352 on sda1 (8 sectors)
kworker/2:0(31017): READ block 4980352 on sdb1 (8 sectors)
uptime :
======Idle 2514 seconds======
Mon Dec 9 08:01:26 CST 2019
#####################################################

carter2005 发表于 2019-12-11 09:48:21

kworker进程是kernel处理任务的进程，属于干活的，不可能是问题的源头，说实话，想要硬盘休眠，群晖上就别装什么套件，就简单文件共享，否则只要有读数据操作，硬盘就得唤醒，群晖没把系统和数据分区放在不同硬盘上，基本无法避免的，硬盘虽然挺耗电的，但群晖硬盘休眠真的挺鸡肋的，反而容易把硬盘弄坏，得不偿失。

查看完整版本: kworker进程导致黑群不能硬盘休眠，请问是什么原因？