November 22, 20196 yr Mover is not moving files anymore, i enabled logging: Nov 22 17:30:43 NAS root: mover: started Nov 22 17:30:43 NAS root: mover: finished No info. There's 170 gb of files not in use in the cache, I have no WMs , no dockers, in fact the service is disabled. There's still space on the array. How do i diagnos the problem? Edited November 22, 20196 yr by je82
November 22, 20196 yr Author 5 minutes ago, Squid said: Post your diagnostics I think i know whats going on, not sure if this is intended function, here's what i did: 1. I moved 170gb of files this morning, i forgot i had cache enabled. 2. I disabled cache to move 6tb+ of files to same array. 3. The 6tb had finished moving, i now realize i have 170gb in my cache i want to move. 4. I click move, nothing happens. The thing is, the drive that had space "open" from before when i moved the files to the cache no longer has space. Allocation method: Fill Up combined with Split Level : Auto split as required. I do not know how the mover works, but once you start move to cache does it queue the files that are suppose to be moved later to a disk that has free space at the time of the files being moved to cache? Then that is the issue here, the files are queued for a drive that does no longer have room. I'll move the files manually, i belive this is a very special cirumstance that probably wont ever happen again. Edited November 22, 20196 yr by je82
November 22, 20196 yr No queuing. At the time it runs, it checks the use cache settings on the share and moves appropriately. Sounds like after disabling the use cache, you never re-enabled it. Edited November 22, 20196 yr by Squid
November 22, 20196 yr Community Expert No, there is no queue. Mover looks at each file dynamically to decide if it should be moved. If mover is not moving files then there is something stopping it from doing so. The reason for asking for the diagnostics was so that we could see what your settings currently are.
November 22, 20196 yr Author 2 minutes ago, Squid said: No queuing. At the time it runs, it checks the use cache settings on the share and moves appropriately. Sounds like after disabling the use cache, you never re-enabled it. Voila, i had no idea if the cache was disabled for the share the mover would not work if triggered manually. I re-enabled the cache and hit move and now it is moving files, noted, thanks for the heads up!
Archived
This topic is now archived and is closed to further replies.