-
[Plugin] Mover Tuning
Hey, thanks for stepping up and getting the plugin to run on 7.0 Unfortunately I got a big problem with this version of the plugin, which results in it being unusable in my setup. For some reason it seems to want to calculate share usage for shares that don't matter at all. For me it's shares that each live on an individual single disk pool with no secondary storage, where I host a storj node each (millions if not billions of small files). I would like an option or workaround to completely ignore such shares on their own pool with no secondary storage. Something like: pool has only one share and the share has no secondary storage -> no need to calculate share usage Because right now it's doing this: Feb 17 18:30:28 Tower move: Primary storage: storjone - size: 19TiB - used: 39 % (7.1TiB) Feb 17 18:30:28 Tower move: Secondary storage: none Feb 17 18:30:28 Tower move: Share Information: Name: storj1 - Path: /mnt/storjone/storj1 Feb 17 18:30:28 Tower move: Mover action: no action, only storjone used (cache:only). Feb 17 18:30:28 Tower move: => Nothing will be moved. Share usage is taken into account in the calculation of the threshold for other shares. Feb 17 18:30:28 Tower move: Calculating share usage... (can take a moment) The calculation of the share usage takes at least a couple of hours and if the disk is busy it was stalled for over a day before I had to stop the mover and run it without the plugin to not completely fill the cache drives. Tried different things with the exclude list but it seems to always trying to calculate share usage before anything else.
-
toyberg90 joined the community
-
[Plugin] Mover Tuning
Hey, I wanted to use the setting "Move files that are greater than this many days old: Auto". Unfortunately this will calculate share usage of shares that have no mover enabled. The shares are on their own single disk pool for a reason, but the mover still is trying to calculate share usage, and on this single disk shares it takes days to calculate share usage. Is there a way to not take single disk shares with cache disabled into account for the calculations of the AUTO settings? Feb 8 09:11:10 Tower move: Primary storage: storjone - size: 19TiB - used: 38 % (6.9TiB) Feb 8 09:11:10 Tower move: Secondary storage: none Feb 8 09:11:10 Tower move: Share Information: Name: storj1 - Path: /mnt/storjone/storj1 Feb 8 09:11:10 Tower move: Mover action: no action, only storjone used (cache:only). Feb 8 09:11:10 Tower move: => Nothing will be moved. Share usage is taken into account in the calculation of the threshold for other shares. Feb 8 09:11:10 Tower move: Calculating share usage... (can take a moment) The second to last line is what I'm referring to. Nothing will be moved but the share usage calculation will take days (and there are more of such single disk shares that come after this one)
toyberg90
Members
-
Joined
-
Last visited