NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS OS Vi.j.k - Discs don't spindown - still
I decided to use generics for the version in the title, so I can resuse this for the next release... Right now it applies to 6.10.1 which I upgraded to yesterday. tl;dr disk spindown is still br...
And what processes are wetting the inodes on e.g. the md device(s)?
This example is not intended to be a "does not spin-down" example, just to illustrate what you might have done and collected as part of your test, and what I would like to see (taken here from the Kernel log rung buffer):
root@RN628X:~# /bin/echo 1 > /proc/sys/vm/block_dump
root@RN628X:~# dmesg | grep dirt | grep md
[382243.814302] kworker/u16:1(28029): dirtied inode 1 (?) on md127
[382267.797468] systemd-journal(2550): dirtied inode 492340 (system.journal) on md0
[382392.192136] aurndb-write-db(4298): dirtied inode 7428 (audit_log.sq3) on md127
[382392.222247] sshd(28139): dirtied inode 11380 (wtmp) on md0
[382392.222272] sshd(28139): dirtied inode 11377 (lastlog) on md0
[382453.937746] btrfs-transacti(2646): dirtied inode 1 (?) on md127
[382568.295864] systemd-journal(2550): dirtied inode 492340 (system.journal) on md0
[382608.754085] loadavg(5756): dirtied inode 11834 (loadavg.dat) on md0
root@RN628X:~# /bin/echo 0 > /proc/sys/vm/block_dump
Please note that a system disconnected from the network can and will develop activities becaue of the disconnected interfaces, because of the lack of Internet connectivity, ... so I would consider your ritual *****.
schumaku wrote:And what processes are wetting the inodes on e.g. the md device(s)?
This example is not intended to be a "does not spin-down" example, just to illustrate what you might have done and collected as part of your test, and what I would like to see (taken here from the Kernel log rung buffer):root@RN628X:~# /bin/echo 1 > /proc/sys/vm/block_dump
root@RN628X:~# dmesg | grep dirt | grep md
[382243.814302] kworker/u16:1(28029): dirtied inode 1 (?) on md127
[382267.797468] systemd-journal(2550): dirtied inode 492340 (system.journal) on md0
[382392.192136] aurndb-write-db(4298): dirtied inode 7428 (audit_log.sq3) on md127
[382392.222247] sshd(28139): dirtied inode 11380 (wtmp) on md0
[382392.222272] sshd(28139): dirtied inode 11377 (lastlog) on md0
[382453.937746] btrfs-transacti(2646): dirtied inode 1 (?) on md127
[382568.295864] systemd-journal(2550): dirtied inode 492340 (system.journal) on md0
[382608.754085] loadavg(5756): dirtied inode 11834 (loadavg.dat) on md0root@RN628X:~# /bin/echo 0 > /proc/sys/vm/block_dump
Please note that a system disconnected from the network can and will develop activities becaue of the disconnected interfaces, because of the lack of Internet connectivity, ... so I would consider your ritual *****.
I've been dealing with this bug for years. Thank you for the complement ***** to you too.
While you might be perfectly right withb the problem, your test is potentially wrong. Other NAS vendors start writing error information into logs, try to send error status information, and much more - and this often wetting the storage buffer and makes the HDD spinning again.
Instead of nagging - answer the question.
My 'ritual' is to try again after each OS release.
Steps involved in the past were based on requests from Netgear.
My system is as vanilla as you can get. Apart from Frontview checking for updates (which is from my PC) it does not talk to the internet.
It does not have scheduled anything that is not vanilla.
Prior to disconnecting the cable, I checked, spinup was premature.
Previously I was challenged that spurious network activity was the cause of the spinups.
I did offer that "Let me know if anyone wants noflushd -b or block_dump info."
However seeing you asked with such a polite post...
Standby...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
