What the heck is mover trying todo?

[praaphorst]

Current syslog, i am confused as why the mover is trying to remove these locations:

 

ower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/PhotoTranscoder/26 Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/PhotoTranscoder/d2 Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/PhotoTranscoder/ab Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/PhotoTranscoder/f9 Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/PhotoTranscoder/7f Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/PhotoTranscoder/dd Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/PhotoTranscoder/c8 Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/PhotoTranscoder Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library/Application Support/Plex Media Server Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library/Application Support Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer/Library Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/PlexMediaServer Directory not empty
May 2 12:00:13 Tower move: skipping file in-use: ./appdata/sabnzbd/admin/history1.db
May 2 12:00:13 Tower root: .d..t...... appdata/sabnzbd/admin/
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/sabnzbd/admin Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/sabnzbd Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/couchpotato/data/database/_indexes Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/couchpotato/data/database Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/couchpotato/data/cache/python Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/couchpotato/data/cache Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/couchpotato/data/custom_plugins Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/couchpotato/data Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/couchpotato Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/deluge/ssl Directory not empty
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata/deluge Directory not empty
May 2 12:00:13 Tower root: .d..t...... appdata/plexpy/
May 2 12:00:13 Tower root: .d..t...... appdata/sonarr/
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata Directory not empty
May 2 12:00:13 Tower root: moving "system" to cache
May 2 12:00:13 Tower move: skipping file in-use: ./system/docker/docker.img
May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./system/docker Directory not empty
May 2 12:00:14 Tower move: skipping file in-use: ./system/libvirt/libvirt.img
May 2 12:00:14 Tower move: rmdir: /mnt/disk1/./system/libvirt Directory not empty
May 2 12:00:14 Tower move: rmdir: /mnt/disk1/./system Directory not empty
May 2 12:00:14 Tower root: mover finished

Edited May 2, 2017 by praaphorst

[HellDiverUK]

Where do you have those shares set up to be?  If they're on disk1 and you have them set to be on disk2, then it's going to want to move them.  Or, if they're supposed to be on the cache drive and are actually on disk1 (which happens to me the odd time if my cache drive changes), then mover can't move when dockers are running.

 

I'd check where the shares are set up to be, and if everything is as it should be, stop ALL your dockers and VMs and try to run mover again.

 

If that doesn't work, then I've found moving things using mc works great.

[JorgeB]

You have those shares on the array and set as cache prefer, move them to cache or set cache to no.

[trurl]

1 hour ago, HellDiverUK said:

If they're on disk1 and you have them set to be on disk2, then it's going to want to move them.

Mover will never move anything from an array disk to another array disk. It only moves from cache to array (cache-yes) or array to cache (cache-prefer).

 

2 hours ago, praaphorst said:

May 2 12:00:13 Tower move: rmdir: /mnt/disk1/./appdata Directory not empty
May 2 12:00:13 Tower root: moving "system" to cache
May 2 12:00:13 Tower move: skipping file in-use: ./system/docker/docker.img

Most likely you have appdata and system set to cache-prefer, as they should be, and it is trying to move the files from array to cache. Did you recently add a cache drive?

 

2 hours ago, HellDiverUK said:

stop ALL your dockers and VMs and try to run mover again.

^This - it can't complete the moves because the files are open.

 

 

[HellDiverUK]

12 minutes ago, trurl said:

Mover will never move anything from an array disk to another array disk. It only moves from cache to array (cache-yes) or array to cache (cache-prefer).

 

 

 

Except when files end up on the wrong drive by some freak, and then it will.  Again, probably due to some bug/confusion in FUSE.

[trurl]

22 minutes ago, HellDiverUK said:

Except when files end up on the wrong drive by some freak, and then it will.  Again, probably due to some bug/confusion in FUSE.

It isn't necessary to have some freak for files to be on a drive that is not included in the user share, since includes/excludes only control where files get written when writing to a user share. It is very simple to write files directly to a drive so that they end up being part of a user share (for reads) that excludes that drive (for writing).

 

I haven't studied the mover script lately. Is there something about cache-prefer handling that would make it move a file from one array drive to another array drive? Possibly due to cache already being full?

 

Do you have an example of this happening?

[HellDiverUK]

I don't, I just chortled to myself about FUSE being confused and carried on with my life.

[praaphorst]

Thank you all for you thoughtful replies, appdata is indeed cache prefer, manually moved some files.