NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS OS V6.9.5 - Discs don't spindown - still
This is turning into a ritual, as for the last few releases I again check whether disc spindown is fixed.
Last was for 6.9.3 here.
My last post there was "So has this been recognised as a bug...
Michael_Oz wrote:
Feb 24 18:16:35 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:16:35 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:16:35 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc
... Feb 24 18:16:42 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:16:42 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc
... Feb 24 18:16:50 ME-NAS-316A kernel: kworker/u8:4(20452): dirtied inode 1 (?) on md0 ... Feb 24 18:16:50 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:16:50 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:16:50 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:16:50 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc ... Feb 24 18:17:10 ME-NAS-316A kernel: systemd-journal(1465): dirtied inode 1 (?) on md0 Feb 24 18:17:10 ME-NAS-316A kernel: systemd-journal(1465): dirtied inode 2036622 (system.journal) on md0 ... Feb 24 18:17:13 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:17:13 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:17:13 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:17:13 ME-NAS-316A kernel: rnutil(21028): dirtied inode 9380 (event.sq3) on md0 ... Feb 24 18:17:15 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:17:15 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:17:15 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc ... Feb 24 18:17:17 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:17:17 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:17:17 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc ... Feb 24 18:17:25 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:17:25 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc Feb 24 18:17:25 ME-NAS-316A kernel: readynasd(3755): dirtied inode 4026532241 (LCD) on proc
I'd be more concerned about these dirtied inode messages than disk spindown.
Though they might be a result of spindown (a consequence of pending writes being cached), I'm not seeing them on my own system (which also has spindown enabled). But it is resyncing at the moment, and it's possible that the log doesn't go back far enough to see them.
StephenB wrote:
... I'm not seeing them on my own system (which also has spindown enabled).Do you have
noflushd -b and
# echo 1 > /proc/sys/vm/block_dump
?
Michael_Oz wrote:
noflushd -b and
# echo 1 > /proc/sys/vm/block_dump
?
No (though at the moment the system is resyncing, so there's no point in doing those at present).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
