-
Diagnostics file not fully anonymized if using ca.mover.tuning
Hi, I just created a diagnostics file for the first time and highly appreciate that they are anonymized by default. I still wanted to check what's in there so I looked at all the files if e.g. the names of my shares appear. Under "shares" in the zip file they are anonymized. But my diagnostics also contained logs/syslog-previous.txt which had the names of the shares in clear-text, supposedly caused by the ca.mover.tuning plugin. My suggestion: I think it would be good if the diagnostics creation tool would try to filter out some system-wide infos that are considered as sensitive, so that users are not getting surprised by data that some plugins might leave in the logs 😅 Jan 25 03:40:01 sparky move: ----------------------------------------------------------- Processing [corp] share --------------------------------------------------------- Jan 25 03:40:01 sparky move: Primary storage: cache - size: 3.5TiB - used: 4 % (163GiB) Jan 25 03:40:01 sparky move: Secondary storage: none Jan 25 03:40:01 sparky move: Share Information: Name: corp - Path: /mnt/cache/corp Jan 25 03:40:01 sparky move: Mover action: no action, only cache used (cache:only). Jan 25 03:40:01 sparky move: => Nothing will be moved. Share usage is taken into account in the calculation of the threshold for other shares. Jan 25 03:40:01 sparky move: Calculating zfs share usage... Jan 25 03:40:01 sparky move: cache/corp used: 140KiB Jan 25 03:40:01 sparky move: -------------------------------------------------------- Processing [corp_Video] share ------------------------------------------------------ Jan 25 03:40:01 sparky move: Settings override: Jan 25 03:40:01 sparky move: ------------------ Jan 25 03:40:01 sparky move: Using share (cache:yes) moving threshold: 0 % Jan 25 03:40:01 sparky move: Using share (cache:yes) freeing threshold: 0 % Jan 25 03:40:01 sparky move: Age: 30 Jan 25 03:40:02 sparky move: ------------------------------------------------------------------------ Jan 25 03:40:02 sparky move: Primary storage: cache - size: 3.5TiB - used: 4 % (163GiB) Jan 25 03:40:02 sparky move: Secondary storage: user0 Jan 25 03:40:02 sparky move: Share Information: Name: corp_Video - Path: /mnt/cache/corp_Video Jan 25 03:40:02 sparky move: Moving threshold: 0% (0B) ; Freeing threshold: 0% (0B) Jan 25 03:40:02 sparky move: Mover action: cache->user0 (cache:yes). Pool is above moving threshold percentage: 4% >= 0%. Jan 25 03:40:02 sparky move: => Will smart move old files from cache to user0. Nothing will be moved from user0 to cache Jan 25 03:40:02 sparky move: Adding Age Jan 25 03:40:02 sparky move: Age (modification time) 30 Jan 25 03:40:02 sparky move: Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2026-01-25T034001.list for corp_Video
-
[Plugin] File Activity – See What’s Keeping Your Unraid Disks Busy
I tried both, but neither of those attempts created any log entries. root@sparky:~# touch /mnt/user/media/test2.txt root@sparky:~# touch /mnt/disk1/media/test3.txt root@sparky:~# cat /mnt/user/media/test2.txt root@sparky:~# cat /mnt/disk1/media/test3.txtTo hopefully log everything I enabled all options and also removed all default exclusions that were configured in the plugin settings and rebooted the whole server - still shows nothing in the logs... One side-note which is probably not related to my issues, but still something that might be relevant for improving the plugin: My Unraid Array is encrypted via LUKS and if I understand the content of fileactivity-watcher.log correct, then the plugin initially fails after a reboot. root@sparky:~# cat /var/log/fileactivity-watcher.log {"level":"info","tag":"2026.01.27.0511","revision":"b682105746dbadde8748552c5e3eab1c47752679","git_dirty":"no","time":1769978020,"message":"Build information"} {"level":"info","time":1769978020,"message":"Starting file activity watcher..."} {"level":"info","Exclusions":[],"Enable":true,"UnassignedDevices":true,"Cache":true,"SSD":true,"DisplayEvents":1000,"MaxRecords":20000,"time":1769978020,"message":"File Activity Watcher Configuration"} {"level":"fatal","error":"open /var/local/emhttp/disks.ini: no such file or directory","time":1769978020,"message":"Error loading disks file"} ### I disabled and re-enabled the "Enable File Activity Monitoring" option to hopefully restart the plugin and re-ran the command: root@sparky:~# cat /var/log/fileactivity-watcher.log {"level":"info","tag":"2026.01.27.0511","revision":"b682105746dbadde8748552c5e3eab1c47752679","git_dirty":"no","time":1769978629,"message":"Build information"} {"level":"info","time":1769978629,"message":"Starting file activity watcher..."} {"level":"info","Exclusions":[],"Enable":true,"UnassignedDevices":true,"Cache":true,"SSD":true,"DisplayEvents":1000,"MaxRecords":20000,"time":1769978629,"message":"File Activity Watcher Configuration"} {"level":"info","array_disks":2,"pool_disks":1,"time":1769978629,"message":"Disk count"} {"level":"warn","error":"open /var/state/unassigned.devices/unassigned.devices.json: no such file or directory","time":1769978629,"message":"Error reading unassigned devices file"} {"level":"info","disk":"disk1","mountpoint":"/mnt/disk1","type":"data","filesystem":"luks:zfs","rotational":true,"time":1769978629,"message":"Watching disk"} {"level":"info","disk":"disk2","mountpoint":"/mnt/disk2","type":"data","filesystem":"luks:zfs","rotational":true,"time":1769978629,"message":"Watching disk"} {"level":"info","disk":"cache","mountpoint":"/mnt/cache","type":"cache","filesystem":"luks:zfs","rotational":false,"time":1769978629,"message":"Watching disk"} {"level":"info","count":3,"time":1769978629,"message":"Watch folders"} {"level":"info","time":1769978629,"message":"Watcher ready"} {"level":"info","time":1769978629,"message":"Starting event listener..."} {"level":"info","current_lines":0,"time":1769978629,"message":"Current activity records"} {"level":"info","path":"/mnt/disk2","fsid":"0bd9a283d2ee9f00","time":1769978629,"message":"Cached mount fsid"} {"level":"info","path":"/mnt/cache","fsid":"0e472f0bf4816100","time":1769978629,"message":"Cached mount fsid"} {"level":"info","path":"/mnt/disk1","fsid":"af6bef5907b23d00","time":1769978629,"message":"Cached mount fsid"}I'll also attach the diagnostics.zip as @trurl requested, maybe that helps. sparky-diagnostics-20260201-2154.zip
-
[Plugin] File Activity – See What’s Keeping Your Unraid Disks Busy
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 config There 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 :)
sparky2025
Members
-
Joined
-
Last visited