dlandon

https://raw.githubusercontent.com/dlandon/file.activity/master/file.activity.plg

Due to some personal circumstances, I am unable to keep the pace I was working with Unraid. I would not resubmit the plugin if I could not maintain it. I said I would not be able to provide a lot of support. A lot of support is provided here by other Unraid users and they do a pretty darn good job of it. I'll provide code fixes as needed. Honestly, this plugin does not require a lot of maintenance. I made the repositiories Private while I assessed my situation. Probably not the best decision, but I am doing the best I can. If anyone wants a refund, I'd be happy to refund your $0 investment. If Unraid chooses not to put it back on CA, that is there decision.

Please don't add any tracking or monitoring to plugins I've written. CA has the capability to monitor the number of times a plugin gets downloaded that will work for the information you want. I am not pleased with the move to tracking and monitoring that has been added to my work. I am re-opening the file activity plugin I wrote and maintained and you can remove the "revised" version and re-install my original version using the URL in the first post. It doesn't track you! I'll also resubmit to CA. I have added a new feature that will let you turn off monitoring SSD devices. Monitoring of file activity was intended to be used to monitor spinner devices and not SSD type devices. Monitoring SSDs overwhelms inotify and is probably the reason for the posts about overwhelming CPU activity. Inotify is not set up to monitor "access" file events as this again will overwhelm inotify. If you install the cache dirs plugin, access events should not cause disk spin ups. I am not in a position to provide a lot of support, but I will do what I can for anyone having issues with my latest version.

Unraid does not recognize the 'sda' device as an unassigned disk. On the UD page, click on the double arrows icon in the upper right of the page and see if Unraid will determine if the disk is unassigned. It will assign the disk device to 'Dev 1', If it doesn't work, go to the UD Settings page and set the logging to 'Udev and Hotplug', then click on the double arrow again. Once you do that, then post the diagnostics again.

Not necessarily, but if you follow the best practices, you should not be experiencing the stale file handles. There may be other users here with Proxmox experience that might be able to offer some suggestions.

The plugin does nothing but set up inotify monitoiring on the files. I have no idea how that can cause high CPU usage unless you are monitoring the nzbget activity. You should't monitor that activity.

Try restarting the recycle bin. I beleive there is an issue when restarting the recycle bin and I'm looking into a solution.

Go to a command line and type 'ud_diagnostics'. Then post the /flash/logs/ud_diagnostics.zip.

There was a recent release of UD Preclear that fixed this situation. Remove and re-install the plugin to see if it clears up the issue. Running from the command line will work, but not recommended

Post diangnostics. Be sure the diagnostics includes where the disks don't auto mount.

The activity is logged and can be seen on the share and disk page organized by share or disk depending on the page. Be sure the 'Status' in the upper right corner shows 'Running'. If you still can't get it working, post your diagnostics.

It works in either situation.

It's difficult for us to help since LT does not support virtualizing Unraid.

That comes from Intel. They recommend Performance (you have that choice), for best overall performance and power savings. The 'Power Saving' mode is good for after hours when performance is not important. You can do this using Tips and Tweaks scheduling. I also recommend turning off Turbo after hours with Tips and Tweaks scheduling.

That means those are the only CPU Governor choices for the 'Intel Pstate' driver. If you saw a change since updating Unraid, then the driver for your processor changed with the latest Linux kernel.