December 10, 2025Dec 10 2 minutes ago, Yusseiin said:I cannot find the original one on the CA :(You can install it from the Plugins tab - Install pluginPastehttps://raw.githubusercontent.com/dlandon/file.activity-next/master/file.activity-next.plgUninstall this one first. Edited December 10, 2025Dec 10 by Niklas
December 10, 2025Dec 10 Just now, Niklas said:You can install it from the Plugins tab - Install pluginPastehttps://raw.githubusercontent.com/dlandon/file.activity/master/file.activity.plgUninstall this one first.It is working fine on 7.2.2? I just need to check file activity on disk.
December 10, 2025Dec 10 Just now, Yusseiin said:It is working fine on 7.2.2? I just need to check file activity on disk.Yes. New name i see with "next" in the name. I updated the url.https://github.com/dlandon/file.activity-nextBut don't use both at the same time. Edited December 10, 2025Dec 10 by Niklas
December 31, 2025Dec 31 The file activity plugin itself is opening some directories on the system, causing my disks spin up. Any clues?Used the following script and got the logwhile true; do OUTPUT=$(lsof /mnt/disk*) if [ -n "$OUTPUT" ]; then echo "$(date '+%H:%M:%S') - Open files detected:" echo "$OUTPUT" echo "----------------------------------------" fi sleep 1doneCOMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAMEfileactiv 19817 root 4r DIR 9,1 4096 2672870747 /mnt/disk1/backup/subdir...----------------------------------------20:55:44 - Open files detected:COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAMEfileactiv 19817 root 4r DIR 9,1 188416 21382526367 /mnt/disk1/backup/subdir...----------------------------------------20:55:48 - Open files detected:COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAMEfileactiv 19817 root 4r DIR 9,1 4096 2652959028 /mnt/disk1/backup/subdir...----------------------------------------20:55:50 - Open files detected:COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAMEfileactiv 19817 root 4r DIR 9,1 4096 5054462461 /mnt/disk1/backup/subdir...----------------------------------------20:55:54 - Open files detected:COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAMEfileactiv 19817 root 4r DIR 9,1 4096 13355131989 /mnt/disk1/backup/subdir...
January 3Jan 3 On 12/10/2025 at 6:05 PM, Niklas said:Yes. New name i see with "next" in the name. I updated the url.https://github.com/dlandon/file.activity-nextBut don't use both at the same time.Sorry for ultra late reply, installed and i am gonna test it.Is indeed running, hope this will find what is making the disk spinningEDIT. : Still not working even with this.The test that i am doing is simple, all the disk stopped, i start a video from plex, one disk start spinning but file activity is not registering it.
January 4Jan 4 10 hours ago, Yusseiin said:Sorry for ultra late reply, installed and i am gonna test it.Is indeed running, hope this will find what is making the disk spinningEDIT. : Still not working even with this.The test that i am doing is simple, all the disk stopped, i start a video from plex, one disk start spinning but file activity is not registering it.Set log open file events to yes. Edited January 4Jan 4 by Niklas
January 4Jan 4 6 hours ago, Niklas said:Set log open file events to yes.Oh my bad, now it is working.Hope it will updated with the filter and sortable logic like file activity v2
January 7Jan 7 I haven't had time to look into it yet, but I'm really looking forward to your revised version of the plugin.
January 15Jan 15 Great plugin, really handy. I had the 'file activity' one installed before and it never worked correctly. Just a bit of feedback - when I select to order the log "by date", it doesn't actually sort the list of entries by date. It still sorts them by either share or disk first, and just sorts those by date/time. Which is fine, it does make sense, but there's no way to quickly scan between shares and disks as it's just a list of like 50 pages and the different shares/disks are in a random place. I assume the intended method (only one I've found anyway) is by turning on and off individual 'group' filters, but that seems like a bit of a workaround rather than a UX method. Not sure on a better solution, maybe have a 'front page' which shows the most recent 20 entries from each share/disk, so that info is all on one page, and then have the existing sort/filters database logs as the next page or a separate tab...I dunno, was just a thought, as I mostly use this to check for things causing my disks to spin up unecessarily etc so I only need to see recent files for each, rather than all the files for each sequentially. Regardless, the plugin works great as it is, thanks for putting the work in!
January 24Jan 24 On 12/10/2025 at 6:05 PM, Niklas said:Yes. New name i see with "next" in the name. I updated the url.https://github.com/dlandon/file.activity-nextBut don't use both at the same time.Does this plug-in show which process is accessing files?I had it installed, but it never showed any results even though my disks were spinned down and back up again a lot of times.I'm on unraid 7.2.3. Edited January 24Jan 24 by bokkoman
January 24Jan 24 Just now, bokkoman said:Does this plug-in show which process is accessing files?I had it installed, but it never showed any results even though my disks were spinned down and back up again a lot of times.I'm on unraid 7.2.3.Does this plug-in show which process is accessing files?I had it installed, but it never showed any results even though my disks were spinned down and back up again a lot of times.I'm on unraid 7.2.3.Both does not show who is accessing the file but knowing what file is getting called can lead to that.If you have no file showing but disk still spinning you could be in the same situation as me.In my case it was ca.mover that was trying to move file from cache to the array but since those file was in an ignored list or being used it was not able to move it, but it was still spinning the disk
January 24Jan 24 24 minutes ago, Yusseiin said:Both does not show who is accessing the file but knowing what file is getting called can lead to that.If you have no file showing but disk still spinning you could be in the same situation as me.In my case it was ca.mover that was trying to move file from cache to the array but since those file was in an ignored list or being used it was not able to move it, but it was still spinning the diskAnd how did you solve this?Or how did you find out it was this plug-in? So i can investigate on my unRAID server
January 24Jan 24 6 minutes ago, bokkoman said:And how did you solve this?Or how did you find out it was this plug-in?So i can investigate on my unRAID server The disks always spun up at the same time, which was the same time the mover was called up.To figure this out, I stopped any app that could access the files (*arr, plex, etc.) and watched the behavior. In the end, it was still doing it, so I also stopped the mover, and in the end, it was him.To solve this, I increased the mover thresholds.
January 24Jan 24 What is lu?And can you perhaps share you mover settings? I have the mover tuning installed as well. I just disabled it for now (mover and mover tuning) to see what happens.
January 24Jan 24 3 hours ago, bokkoman said:What is lu?And can you perhaps share you mover settings?I have the mover tuning installed as well. I just disabled it for now (mover and mover tuning) to see what happens.It was him* My settings are this
January 24Jan 24 Author I do plan to add PID reporting soon (to see what process is accessing files), I just haven’t had the time to do it yet.
January 24Jan 24 Just now, bokkoman said:Do you know which settings was the bad guy?There were no bad settings, the problem was that i have 75% threshold and an ignore file.If your cache reach > 75% every x time ( 1 hours in my case ) the mover tries to empty it.This behavior is intended.The problem is that if this > 75% is made with file that are being ignored by the mover ( they are in the ignore list or they are being used ) the moving is getting triggered making your array drive spinning, but it wont move anything.This is getting an infinite loop until the cache reach a value <75%
February 1Feb 1 Hi! I got some seemingly random disk spin ups on my Unraid server. Looks like this plugin could be able to pinpoint the source of that. But I get no log entries at all, which is weird. Maybe I'm missing something or my system is not compatible (using ZFS as the filesystem). Screenshot of my plugin configThere are 0 entries in "Disk Activity" and "Share Activity". I did some manual activity (browsing and opening files via SMB share, ran touch and cat to create and read files), but still no entries. Any ideas? Much appreciated, thanks :)
February 1Feb 1 2 hours ago, sparky2025 said:random disk spin upsAttach Diagnostics ZIP to your NEXT post in this thread.I may split these into their own thread after looking at diagnostics.
February 1Feb 1 Author 2 hours ago, sparky2025 said:Hi! I got some seemingly random disk spin ups on my Unraid server. Looks like this plugin could be able to pinpoint the source of that.But I get no log entries at all, which is weird. Maybe I'm missing something or my system is not compatible (using ZFS as the filesystem).Screenshot of my plugin configThere are 0 entries in "Disk Activity" and "Share Activity". I did some manual activity (browsing and opening files via SMB share, ran touch and cat to create and read files), but still no entries. Any ideas? Much appreciated, thanks :)Are you creating the file on a pool, or on /mnt/diskX, /mnt/user/ ?I'd start by turning the "Enable" features on and removing the exclusions if you want to get a better sense of what's accessing the disks.
February 1Feb 1 I have noticed this version not always works. Stops logging in some case I don't know. Still using file.activity-next.plg (enable for open file events and make sure "Status: Running" if trying that one out).With ZFS in the array, set atime=off to prevent that sort of spin up too (that won't show up in these tools) Edited February 1Feb 1 by Niklas
February 1Feb 1 Author 6 minutes ago, Niklas said:I have noticed this version not always works. Stops logging in some case I don't know. Still using file.activity-next.plg (enable for open file events and make sure "Status: Running" if trying that one out).With ZFS in the array, set atime=off to prevent that sort of spin up too (that won't show up in these tools)Please stop advertising the other plugin in my support thread.
February 1Feb 1 2 minutes ago, EDACerton said:Please stop advertising the other plugin in my support thread."Advertising". Ok.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.