tjr

Forgot to swap from Array to Cache for mover, fixed - attached. raider-diagnostics-20250428-1710.zip

Sorry was away for the weekend. See attached for new diags. raider-diagnostics-20250428-1322.zip

Finished - see attached for logs. raider-diagnostics-20250424-1957.zip

Sure, will that configuration not fill up the Cache drive though? Or does it automatically shuffle files back to the Array once they're not in use?

Yep, disabled docker/VM already once I started the move job. My shares are set up in the following manner:

The Dockers do, yes. I mostly have cache as "fast storage" which then is scheduled hourly to move the files over. Generally it's only a few GB at a time, only this large since I suppose it hasn't been running for a extended amount of time.

This was installed a few revisions back when I wanted it to be scheduled with certain exclusions, if it's native now there's no need to have it.

Running now, log is showing files moving so progress is being made.

root@RAIDer:~# du -h -d 1 /mnt/cache 19G /mnt/cache/domains 121M /mnt/cache/system 4.8G /mnt/cache/appdata 923G /mnt/cache/data 947G /mnt/cache

Yes, the user share is named "data" and is where the majority of files are.

Please see attached raider-diagnostics-20250424-1340.zip

Noticed today that my cache drive was filled up and mover is not working. Syslog shows the following when trying to use mover but doesn't do anything: Usage: /usr/local/sbin/mover.old start [-e] <disk_name> Apr 24 13:29:50 RAIDer move: /usr/local/sbin/mover.old stop|status Apr 24 13:29:50 RAIDer move: <disk_name> must match pattern 'disk[0-9]*'