Mover: share cache full

[Jaybau]

When running "Mover" I receive this error message:

 

Tower shfs: share cache full

 

Not sure if the above message is telling me the "share" is full or the "cache" drive is full.  I assume the share.  Logs do not tell me which share; I assume "media".

 

Log Info:
 

mover: started
Usage: grep [OPTION]... PATTERNS [FILE]...
find: ‘standard output’: Broken pipe
find: write error
mover: finished

 

Share Settings (Allocation Method = High-water):

 

 

Is the mover trying to move only to Disk 1 (because of the "high water" allocation method)?  But fails because Disk 1 is below the 25 GB minimum free space?

 

Will mover try to move to Disk 2 or Disk 3, when high water allocation is no longer viable?

 

Should I choose a different allocation method?

 

The reason why the disks are not balanced, despite "high water" allocation, is because I have add disks at different points of time.

 

 

 

 

 

tower-diagnostics-20240325-0932.zip

[JorgeB]

15 minutes ago, Jaybau said:

share cache full

It means the it's hitting the set share floor, i.e., the pool free space is less than the share's minimum free space.

[Jaybau]

8 minutes ago, JorgeB said:

It means the it's hitting the set share floor, i.e., the pool free space is less than the share's minimum free space.

The pool/array's free space is 8.61 TB, and the share floor is 25 GB.

What is causing the error message?

[JorgeB]

That has nothing to do with the array or mover, some share with cache=yes is bypassing the pool when new data is written to that share (not from the mover) and logging that warning,  because it hit the minimum floor setting, cannot tell which share based on the warning, but if you look at the time stamps you may be able to know to which share you were writing to.

[Jaybau]

I'm only getting the error message when I manually run the mover.

# mover
Log Level: 1
mover: started
Usage: grep [OPTION]... PATTERNS [FILE]...
Try 'grep --help' for more information.
find: ‘standard output’: Broken pipe
find: write error
mover: finished

 

I've been writing a lot of data to the "media" share, which first goes to cache, then moves to array.  I'm trying to get the data moved off cache and onto array.  But the mover won't move it, because of the error.

 

I suppose it is possible I'm trying to move something off the array onto the cache, which is failing the mover.  Or something else is trying to move off the cache onto the array, but hitting a minimum floor (haven't found it yet). 

 

In a bind right now, because I need to move data off the cache, cache is filled up, but the mover gets an error. 

 

[JorgeB]

22 minutes ago, Jaybau said:

But the mover won't move it, because of the error.

Enable mover logging, run the mover, post new diags.

[Jaybau]

Finally got the mover to work.  I'm using moving tuning plugin.

To get this to work, I configured the "Mover Tuning - Share Settings".

 

Mover Tuning Config (global):

moverDisabled="no"
moverNice="0"
moverIO="-c 2 -n 0"
threshold="0"
age="no"
sizef="no"
sparsnessf="no"
filelistf="yes"
filetypesf="yes"
filetypesv="*.duplicate,*parts,*.bak,*.qb!,*.tmp, .Recycle.Bin, /mnt/cache/media/.Recycle.Bin"
parity="no"
enableTurbo="no"
logging="yes"
force="no"
ignoreHidden="no"
beforeScript=""
afterScript=""
omovercfg="no"
movenow="yes"
testmode="no"
filelistv=""

 

Mover Tuning - Share Settings

 

moverOverride="yes"
age="no"
sizef="no"
sparsnessf="no"
filelistf="no"
filetypesf="no"
ignoreHidden="no"
omovercfg="no"

 

 

 

[JorgeB]

Just now, Jaybau said:

I'm using moving tuning plugin.

I recommend you always temporarily uninstall that first if you find mover issues, it impossible for us to help it the issues is the plugin, or its settings, we can just help with the stock mover, for help with the plugin you can post in the plugin support thread.