Overnight my cache drive filled up and the mover is failing to run. Each hour the below log entries appear, attempting to run the mover manually produces the same logs. CA Mover Tuning is installed, not sure if that's relevant. Not sure why mover would be attempting to destroy datasets, as that clearly isn't desirable, so it's good that it fails. This is also only 3 out of 11 datasets on the cache, 10 of which are mounted, 6 of which should be acted on by the mover.

 

Feb 27 03:48:49 Global-Dynamics shfs: share cache full
Feb 27 03:52:58 Global-Dynamics shfs: share cache full
Feb 27 04:00:02 Global-Dynamics root: Starting Mover
Feb 27 04:00:02 Global-Dynamics root: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start 3 0 0 '' '' '' '' no 80 '' 'yes' 50
Feb 27 04:00:02 Global-Dynamics shfs: /usr/sbin/zfs unmount 'cache/software'
Feb 27 04:00:02 Global-Dynamics shfs: /usr/sbin/zfs destroy 'cache/software'
Feb 27 04:00:02 Global-Dynamics root: cannot destroy 'cache/software': dataset is busy
Feb 27 04:00:02 Global-Dynamics shfs: retval: 1 attempting 'destroy'
Feb 27 04:00:02 Global-Dynamics shfs: /usr/sbin/zfs mount 'cache/software'
Feb 27 04:00:02 Global-Dynamics shfs: /usr/sbin/zfs unmount 'cache/isos'
Feb 27 04:00:02 Global-Dynamics shfs: /usr/sbin/zfs destroy 'cache/isos'
Feb 27 04:00:03 Global-Dynamics root: cannot destroy 'cache/isos': dataset is busy
Feb 27 04:00:03 Global-Dynamics shfs: retval: 1 attempting 'destroy'
Feb 27 04:00:03 Global-Dynamics shfs: /usr/sbin/zfs mount 'cache/isos'
Feb 27 04:00:03 Global-Dynamics shfs: /usr/sbin/zfs unmount 'cache/devon'
Feb 27 04:00:03 Global-Dynamics shfs: /usr/sbin/zfs destroy 'cache/devon'
Feb 27 04:00:03 Global-Dynamics root: cannot destroy 'cache/devon': filesystem has children
Feb 27 04:00:03 Global-Dynamics root: use '-r' to destroy the following datasets:
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-01-18-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-22-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-15-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-18-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-20-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-17-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-01-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-26-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-01-11-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-24-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-13-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-08-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-27-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-01-25-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-01-04-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-25-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-19-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-14-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-23-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-16-000000
Feb 27 04:00:03 Global-Dynamics root: cache/devon@2024-02-21-000000
Feb 27 04:00:03 Global-Dynamics shfs: retval: 1 attempting 'destroy'
Feb 27 04:00:03 Global-Dynamics shfs: /usr/sbin/zfs mount 'cache/devon'

 

Attach Diagnostics to your NEXT post in this thread.

1 minute ago, Renegade605 said:

Not sure why mover would be attempting to destroy datasets

That's normal, after all data is moved from the dataset.

 

1 minute ago, Renegade605 said:

CA Mover Tuning is installed, not sure if that's relevant.

Start by uninstalling that and retrying, if the same see here first:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=972660

 

 

3 minutes ago, JorgeB said:

That's normal, after all data is moved from the dataset.

It absolutely should not be doing that, and it never has before. Datasets have settings that need to be maintained, not just data.

 

3 minutes ago, JorgeB said:

Start by uninstalling that and retrying, if the same see here first:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=972660

I'd rather not unless absolutely necessary; there are filtered files that shouldn't be moved. Enabling mover logging doesn't provide any additional information.

 

Feb 27 08:06:02 Global-Dynamics root: Starting Mover
Feb 27 08:06:02 Global-Dynamics root: ionice -c 2 -n 7 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start 3 0 0 '' '' '' '' no 80 '' 'yes' 50
Feb 27 08:06:02 Global-Dynamics move: Log Level: 1
Feb 27 08:06:02 Global-Dynamics move: mover: started
[Same Lines As Before]
Feb 27 08:06:03 Global-Dynamics move: mover: finished

 

1 hour ago, Renegade605 said:

and it never has before.

I'm afraid it always does that, and it always did, when the dataset is empty.

I have isolated the cause and will address it in the mover tuning plugin thread. 

That's why I always say, and have added to the FAQ

1 hour ago, JorgeB said:

Start by uninstalling that and retrying

 

13 minutes ago, JorgeB said:

That's why I always say, and have added to the FAQ

Start by uninstalling that and retrying

That wouldn't actually solve the problem though, and I found the cause without doing that. Maybe a good step for novice users, but not for experienced ones.

14 minutes ago, Renegade605 said:

That wouldn't actually solve the problem though

No, but it would confirm the problem is related to that, no point in other users wasting time trying to see if the problem is somewhere else, I don't just ask for asking, I ask because it's a recurring issue, so we need to rule that out first.

3 minutes ago, JorgeB said:

No, but it would confirm the problem is related to that

I get that, but "disable custom configuration and let the OS run wild on your data" is a pretty nuclear option that I wouldn't take as a first step.