File Activity Plugin - How can I figure out what keeps spinning up my disks?


dlandon

Recommended Posts

1 hour ago, dlandon said:

Separate them how?

A separate Option. I can activated this Plugin/File Activity for Cache or for Array or for Cache & Array. At the moment I can activated this only for Cache & Array.

 

1 hour ago, dlandon said:

What is your use case for a feature such as this?

You could then exclude the Docker directory, for example. If you use the Docker Directory instead of the single img there are too many files/operations to get anything useful out of the file activity. Since the directory is individual, you can't do a global exclude like with AppData.

Link to comment
17 minutes ago, Revan335 said:

A separate Option. I can activated this Plugin/File Activity for Cache or for Array or for Cache & Array. At the moment I can activated this only for Cache & Array.

Not true.  Enabling the plugin monitors activity for the Array.  The 'Enable for Cache and Pool Disks?' adds monitoring for any Cache and Pool disks.  Leave it off and only Array disks are monitored.

 

The plugin excludes the 'appdata' and 'syslog' shares automatically.  I should add 'system' to those though so the docker and VM images get excluded.  I'll fix this in the next release.

 

If you do a non traditional mapping of appdata, syslog, and system shares, the file activity plugin will monitor those.

  • Thanks 1
Link to comment
3 hours ago, dlandon said:

Not true.  Enabling the plugin monitors activity for the Array.  The 'Enable for Cache and Pool Disks?' adds monitoring for any Cache and Pool disks.  Leave it off and only Array disks are monitored.

 

The plugin excludes the 'appdata' and 'syslog' shares automatically.  I should add 'system' to those though so the docker and VM images get excluded.  I'll fix this in the next release.

 

If you do a non traditional mapping of appdata, syslog, and system shares, the file activity plugin will monitor those.

Great!
Many, many thanks!

 

Can you maybe put this in the description of the plugin and the hints of the individual functions? Then others will understand it better. I had assumed that you need this option to use the monitoring, because it activates array/cache.

And that with Enable Plugin Monitoring you have to turn on the plugin itself and then choose from the options below what you want to monitor.

 

Thanks for the correction!

Link to comment

I have found a minor bug.

 

With 'Log Activity by Disk or Share?' set to 'Share' I have duplicate entries being displayed.

I have a share called 'sqwrl' and I also have a share called 'email' with a subdirectory 'email/sqwrl'. When files in my email area change they are reported twice, once for each of the two shares.

e.g.

** /mnt/user/sqwrl **

Jun 27 21:45:33 OPEN => /mnt/disk5/email/sqwrl/dovecot.index.log

** /mnt/user/email **

Jun 27 21:45:33 OPEN => /mnt/disk5/email/sqwrl/dovecot.index.log

 

It appears that the per share filtering is being a touch simplistic and picking up the share string in *any* part of the file path, not just the third element after /mnt/disk<n>/.

Link to comment
  • 2 months later...

Actually had a bit of a look at it last night and i noticed in the syslog im getting:

Sep 15 18:45:05 Vault file.activity: Starting File Activity
Sep 15 18:45:05 Vault file.activity: File Activity inotify starting
Sep 15 18:45:16 Vault inotifywait[29573]: Failed to watch /mnt/disk3; upper limit on inotify watches reached!
Sep 15 18:45:16 Vault inotifywait[29573]: Please increase the amount of inotify watches allowed per user via `/proc/sys/fs/inotify/max_user_watches'.
Sep 15 18:45:17 Vault file.activity: File Activity inotify exiting

 

After a bit of searching i ended up increasing the inotify watches, gradually each time it would take longer to exit but eventually when i upped it to just over 4mil i started to get:

Sep 13 20:46:47 Vault file.activity: Starting File Activity
Sep 13 20:46:47 Vault file.activity: File Activity inotify starting
Sep 15 20:49:18 Vault inotifywait[23057]: Couldn't watch /mnt/disk3: No such file or directory
Sep 15 20:49:20 Vault file.activity: File Activity inotify exiting

 

After that ran out of time to keep looking into it

but /mnt/disk3 is there and is healthy so not sure why id get that error

 

edit:

Playing with it tonight again i turned off include cache/pools and how getting

Sep 16 18:46:00 Vault inotifywait[28045]: Failed to watch /mnt/disk4; upper limit on inotify watches reached!

Seems like just increasing the watches is masking another problem?

Edited by macmanluke
Link to comment
3 hours ago, macmanluke said:

Actually had a bit of a look at it last night and i noticed in the syslog im getting:

Sep 15 18:45:05 Vault file.activity: Starting File Activity
Sep 15 18:45:05 Vault file.activity: File Activity inotify starting
Sep 15 18:45:16 Vault inotifywait[29573]: Failed to watch /mnt/disk3; upper limit on inotify watches reached!
Sep 15 18:45:16 Vault inotifywait[29573]: Please increase the amount of inotify watches allowed per user via `/proc/sys/fs/inotify/max_user_watches'.
Sep 15 18:45:17 Vault file.activity: File Activity inotify exiting

 

After a bit of searching i ended up increasing the inotify watches, gradually each time it would take longer to exit but eventually when i upped it to just over 4mil i started to get:

Sep 13 20:46:47 Vault file.activity: Starting File Activity
Sep 13 20:46:47 Vault file.activity: File Activity inotify starting
Sep 15 20:49:18 Vault inotifywait[23057]: Couldn't watch /mnt/disk3: No such file or directory
Sep 15 20:49:20 Vault file.activity: File Activity inotify exiting

 

After that ran out of time to keep looking into it

but /mnt/disk3 is there and is healthy so not sure why id get that error

 

edit:

Playing with it tonight again i turned off include cache/pools and how getting

Sep 16 18:46:00 Vault inotifywait[28045]: Failed to watch /mnt/disk4; upper limit on inotify watches reached!

Seems like just increasing the watches is masking another problem?

Post diagnostics so I can have a closer look.

Link to comment

Hello,

Reading the NerdPack thread, users are recommending to put your packages inside /boot/extra and uninstall NerdPack since it is not going to be working on version 6.11.

I did this, and put on my /boot/extra the following files:
glib2-2.46.2-x86_64-2.txz

glibc-2.33-x86_64-5.txz

perl-5.34.0-x86_64-1.txz

 

Rebooted and I see that perl was installed and my Auto Fan plugin works fine.

The File Activity on the other hand stopped working, giving this error:
 

Sep 25 20:37:47 Tower ool www[4948]: /usr/local/emhttp/plugins/file.activity/scripts/rc.file.activity 'update'
Sep 25 20:37:47 Tower file.activity: Stopping File Activity
Sep 25 20:37:47 Tower file.activity: File Activity is not running
Sep 25 20:37:47 Tower file.activity: Starting File Activity
Sep 25 20:37:47 Tower atd[8547]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /lib64/libpthread.so.0)
Sep 25 20:37:47 Tower atd[8547]: PAM adding faulty module: /lib64/security/pam_unix.so
Sep 25 20:37:47 Tower kernel: atd[8547]: segfault at 0 ip 000014cb08ca2899 sp 00007fff79fbb5f0 error 4 in libpthread-2.33.so[14cb08ca2000+f000]
Sep 25 20:37:47 Tower kernel: Code: 00 48 c7 82 e8 02 00 00 e0 ff ff ff b8 11 01 00 00 66 48 0f 6e c7 66 0f 6c c0 0f 11 82 d8 02 00 00 0f 05 48 8b 05 27 57 01 00 <48> 8b 00 64 48 89 04 25 98 06 00 00 0f b6 05 5c 5a 01 00 64 88 04
Sep 25 20:37:51 Tower ool www[3881]: /usr/local/emhttp/plugins/file.activity/scripts/rc.file.activity 'start'
Sep 25 20:37:51 Tower file.activity: Starting File Activity
Sep 25 20:37:51 Tower atd[8834]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /lib64/libpthread.so.0)
Sep 25 20:37:51 Tower atd[8834]: PAM adding faulty module: /lib64/security/pam_unix.so
Sep 25 20:37:51 Tower kernel: atd[8834]: segfault at 0 ip 000014cb08ca2899 sp 00007fff79fbb5f0 error 4 in libpthread-2.33.so[14cb08ca2000+f000]
Sep 25 20:37:51 Tower kernel: Code: 00 48 c7 82 e8 02 00 00 e0 ff ff ff b8 11 01 00 00 66 48 0f 6e c7 66 0f 6c c0 0f 11 82 d8 02 00 00 0f 05 48 8b 05 27 57 01 00 <48> 8b 00 64 48 89 04 25 98 06 00 00 0f b6 05 5c 5a 01 00 64 88 04
Sep 25 20:37:59 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin checkall
Sep 25 20:38:00 Tower kernel: vethfc91575: renamed from eth0
Sep 25 20:38:00 Tower kernel: eth0: renamed from vethacb0ddf
Sep 25 20:38:22 Tower ool www[4948]: /usr/local/emhttp/plugins/file.activity/scripts/rc.file.activity 'start'
Sep 25 20:38:22 Tower file.activity: Starting File Activity
Sep 25 20:38:22 Tower atd[10530]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /lib64/libpthread.so.0)
Sep 25 20:38:22 Tower atd[10530]: PAM adding faulty module: /lib64/security/pam_unix.so

 

Can the Author of the plugin make it work with glibc version 2.33, it seems the plugin works with version 2.32, but when I try to put v2.32 on the boot/extra, the GUI never comes up.

 

Please let me know if you need more info from me.

I'm still running 6.9.2

 

Thanks.

Link to comment
8 hours ago, hrv231 said:

Hello,

Reading the NerdPack thread, users are recommending to put your packages inside /boot/extra and uninstall NerdPack since it is not going to be working on version 6.11.

I did this, and put on my /boot/extra the following files:
glib2-2.46.2-x86_64-2.txz

glibc-2.33-x86_64-5.txz

perl-5.34.0-x86_64-1.txz

 

Rebooted and I see that perl was installed and my Auto Fan plugin works fine.

The File Activity on the other hand stopped working, giving this error:
 

Sep 25 20:37:47 Tower ool www[4948]: /usr/local/emhttp/plugins/file.activity/scripts/rc.file.activity 'update'
Sep 25 20:37:47 Tower file.activity: Stopping File Activity
Sep 25 20:37:47 Tower file.activity: File Activity is not running
Sep 25 20:37:47 Tower file.activity: Starting File Activity
Sep 25 20:37:47 Tower atd[8547]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /lib64/libpthread.so.0)
Sep 25 20:37:47 Tower atd[8547]: PAM adding faulty module: /lib64/security/pam_unix.so
Sep 25 20:37:47 Tower kernel: atd[8547]: segfault at 0 ip 000014cb08ca2899 sp 00007fff79fbb5f0 error 4 in libpthread-2.33.so[14cb08ca2000+f000]
Sep 25 20:37:47 Tower kernel: Code: 00 48 c7 82 e8 02 00 00 e0 ff ff ff b8 11 01 00 00 66 48 0f 6e c7 66 0f 6c c0 0f 11 82 d8 02 00 00 0f 05 48 8b 05 27 57 01 00 <48> 8b 00 64 48 89 04 25 98 06 00 00 0f b6 05 5c 5a 01 00 64 88 04
Sep 25 20:37:51 Tower ool www[3881]: /usr/local/emhttp/plugins/file.activity/scripts/rc.file.activity 'start'
Sep 25 20:37:51 Tower file.activity: Starting File Activity
Sep 25 20:37:51 Tower atd[8834]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /lib64/libpthread.so.0)
Sep 25 20:37:51 Tower atd[8834]: PAM adding faulty module: /lib64/security/pam_unix.so
Sep 25 20:37:51 Tower kernel: atd[8834]: segfault at 0 ip 000014cb08ca2899 sp 00007fff79fbb5f0 error 4 in libpthread-2.33.so[14cb08ca2000+f000]
Sep 25 20:37:51 Tower kernel: Code: 00 48 c7 82 e8 02 00 00 e0 ff ff ff b8 11 01 00 00 66 48 0f 6e c7 66 0f 6c c0 0f 11 82 d8 02 00 00 0f 05 48 8b 05 27 57 01 00 <48> 8b 00 64 48 89 04 25 98 06 00 00 0f b6 05 5c 5a 01 00 64 88 04
Sep 25 20:37:59 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin checkall
Sep 25 20:38:00 Tower kernel: vethfc91575: renamed from eth0
Sep 25 20:38:00 Tower kernel: eth0: renamed from vethacb0ddf
Sep 25 20:38:22 Tower ool www[4948]: /usr/local/emhttp/plugins/file.activity/scripts/rc.file.activity 'start'
Sep 25 20:38:22 Tower file.activity: Starting File Activity
Sep 25 20:38:22 Tower atd[10530]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /lib64/libpthread.so.0)
Sep 25 20:38:22 Tower atd[10530]: PAM adding faulty module: /lib64/security/pam_unix.so

 

Can the Author of the plugin make it work with glibc version 2.33, it seems the plugin works with version 2.32, but when I try to put v2.32 on the boot/extra, the GUI never comes up.

 

Please let me know if you need more info from me.

I'm still running 6.9.2

 

Thanks.

 

Do not install glibc or glib2.  Glibc 2.36 is already installed in Unraid.  Installing a different version of glibc causes all sorts of problems like this.

root@BackupServer:~# ls /var/log/packages/glibc-2.36-x86_64-3_LT 
/var/log/packages/glibc-2.36-x86_64-3_LT

The log message is misleading.

 

Perl is already installed in 6.11.

 

Remove those packages from /boot/extra/ and reboot.

  • Thanks 1
Link to comment

Thank you @dlandon

 

I removed those packages and had to upgrade from 6.9.2 to 6.11.0

It is a big jump, but the plugin is working now.

 

Now to check all the other plugins...

 

5 hours ago, dlandon said:

Do not install glibc or glib2.  Glibc 2.36 is already installed in Unraid.  Installing a different version of glibc causes all sorts of problems like this.

root@BackupServer:~# ls /var/log/packages/glibc-2.36-x86_64-3_LT 
/var/log/packages/glibc-2.36-x86_64-3_LT

The log message is misleading.

 

Perl is already installed in 6.11.

 

Remove those packages from /boot/extra/ and reboot.

 

Link to comment
  • 3 weeks later...

@dlandon

 

Hi,I love your plugin and really use this often to look up why some disks spin up. I have one request for you though: If the log is very long, the buttons for refresh, delete etc are always below the log and you have to scroll down. I have changed my local FileActivity.page accordingly and am very happy. Whenever I update this change is gone of course. I think above the log they are better kept. Here the corresponding part of my FileActivity.page: https://pastebin.com/sr6uiAf8 

Thank you

Link to comment
1 hour ago, Joe6pack said:

@dlandon

 

Hi,I love your plugin and really use this often to look up why some disks spin up. I have one request for you though: If the log is very long, the buttons for refresh, delete etc are always below the log and you have to scroll down. I have changed my local FileActivity.page accordingly and am very happy. Whenever I update this change is gone of course. I think above the log they are better kept. Here the corresponding part of my FileActivity.page: https://pastebin.com/sr6uiAf8 

Thank you

I agree with you, but doing that is not consistent with the rest of Unraid.  I would suggest you submit an UnraId feature request to have the buttons moved to the top on all log pages.

Link to comment
20 minutes ago, dlandon said:

I agree with you, but doing that is not consistent with the rest of Unraid.  I would suggest you submit an UnraId feature request to have the buttons moved to the top on all log pages.

Settings - Display Settings, Listing Height: Fixed parks the buttons at the bottom of the page and you can scroll around without losing the buttons (eg: Tools, Syslog etc).  No idea if File Activity honors that setting though.

Link to comment
16 hours ago, Squid said:

Settings - Display Settings, Listing Height: Fixed parks the buttons at the bottom of the page and you can scroll around without losing the buttons (eg: Tools, Syslog etc).  No idea if File Activity honors that setting though.

This solution is perfect. Sorry I did not know that there is this setting. Thank you all

 

Edit: Maybe @dlandon can change the calculation for the innerheight of the log window from:

$(function() {
  $('pre.up').css('height',Math.max(window.innerHeight-280,370)).show();
});

to

$(function() {
  $('pre.up').css('height',Math.max(window.innerHeight-320,370)).show();
});

so that the Buttons no longer are half covered by the status bar

Edited by Joe6pack
Link to comment
  • 3 weeks later...

Trying to figure out why after changing the SAS card and backplane (from LSI / 846 expander backplane to an adaptec direct attach since I was bandwidth limited) my array drives keep spinning up.

 

I tried enabling this plugin but I have 2 drives with several million files and it takes FOREVER to start the process and wants to crash even if it does complete.

 

How can I exclude a drive from the activity monitoring? These drives are set to not spin down anyways so I am not worried about them.

 

Thanks

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.