Mover moving log file and preventing HDD spin down

[raphael1-w]

Hi all, 

 

I have a problem regarding the mover moving the nextcloud log file from the cache to the array, which is preventing my HDD from spinning down, and I don't know why it's happening. 

 

The nextcloud container logging has prevented my HDD from spinning down for long periods of time, with them spinning back up ~3 mins after spinning down, every hour. I have successfully solved this by changing the location of the log file to '/config/log/nextcloud.log', and by running the following commands:

docker exec -it nextcloud bash
sudo -u abc touch /config/log/nextcloud.log
chmod 777 /config/log/nextcloud.log

From here

 

However, every time the mover runs, the problem returns. I assume the problem is because the mover is moving the file, which is on the cache, back to the array. I have tried to prevent the move by using the mover tuning plugin and excluding the files '/mnt/cache/Nextcloud/nextcloud.log and '/mnt/cache/./Nextcloud/nextcloud.log'. Even though the mover logs show that the log file has not been moved, the problem still returned. If I move the whole Nextcloud data share from the array back to the cache, the problem goes away. 

Can someone tell me what might have caused this? 

 

Thanks in advance. 

server-r1-diagnostics-20240815-0041.zip

[Kilrah]

Did you check your new log file (supposedly on a cache-only location) is the one that's getting used and the old hasn't been modified since?

[raphael1-w]

I wasn't able to find a different log file anywhere else after running the mover.

 

/config/log/nextcloud.log is in appdata, which is set to cache only. The only log file I could find was in /mnt/cache/appdata/nextcloud/log. I could not find a log file in either /user0 or /disk1. 

[Kilrah]

Then the log being moved isn't your problem anymore.

[raphael1-w]

How so? It's clearly causing a problem, making my drives spin down and up unnecessarily for ~20 times a day, wasting drive life and electricity. 

 

I'm genuinely curious why you think the log being moved isn't my problem. 

[Kilrah]

Since you say you confirmed the log is not on one of the spinning drives it has to be something else?

Maybe try the "open files" plugin...

[raphael1-w]

I might have explained it a bit poorly. Let me try again. 

 

Nextcloud writing to the logs was the cause of my HDD not spinning down. I'm fairly certain about this because the first time I ran those commands to make a new log file, I had most of the data on the array. That solved the problem until the mover ran that night. I have also managed to replicate this one other time, with that being the only other time. 

 

I was not able to find the log on the array, but that might be a me problem because I'm honestly still not that familiar with the file structure, and might have missed the file. 

 

Also, regarding open files, it did not show that nextcloud.log was open anywhere.