I imagine the suspension is only processes which require disk space - eg decryption. Relocation only modifies the file system pointers, no actual data movement.
BH, your logic is impeccable.
You would indeed think that as filing requires no new disk space, then a filing process would work regardless of disk space. Unfortunately this situation is counter-intuitive ...
I just set up and ran a few tests - on a 1TB Humax HDR with only 10GB free space, my
sweeper rules don't activate. The films, single files and folders sit unmoved in the root level. Auto-log says
'Insufficient disk space'. Re-activating
seriesfiler makes the folders disappear with the contents moved to matching sub-folders, however the films and other single files remain. Once there is 40GB free disk space, auto-processing resumes and
sweeper activates successfully.
I realise the moral of the story is never to leave so little free disk space, for this and many other reasons. (I've noticed over the last year, with the aid of the reallocated sector alert, that reallocated sectors occur far more frequently when the disk space is very low)
However sometimes in a busy house disk space can run low from time to time, and
seriesfiler will still work its 'magic', so although
sweeper is far cleverer and more versatile and integrated with the auto processes, it seems that '
sweeper fileunder' is not a straight like for like swap for
seriesfiler.