ReadyNAS OS Vi.j.k - Discs don't spindown - still

---

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 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 *****.

---

I've been dealing with this bug for years. Thank you for the complement ***** to you too.