-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to stop creating new plots as dst becomes full #121
Comments
When using the development branch with multiple destination drives, plotman stopped scheduling plots for a full drive. I had archive disabled. Have you tested the development branch for this capability? |
Hmm I'm not sure this is actually true... I wonder if something else stopped it from plotting? @altendky is there actually anything in dev branch that would do this? Assuming it is still an open issue, @13thProgression you may want to subscribe to #176 As for the original issue
sounds different from
The former could be seen as a request to factor in DST empty space when choosing which drive to plot to, while the later is the same issue as #176 @mikehw care to chime in with more details? |
I created a PR #122 which is meant to address this. #176 is identical. When archiving is off there is no way to have plotman automatically exclude dst drives which are full.
I just mean to say that free space on the dst is never considered when selecting which drive to send the plot to. I don’t intend to change the balancing logic when the drive can receive a plot, but it needs to be evaluated to exclude drives which will be full. |
Currently free space on destination directories is not evaluated when determining which destination directory to select.
Having the option to not plot to full drives would be nice for users that aren't utilizing archiving and want to stop plotting once the destination directories are full. This should be off by default since archiving should free up space while the plot is being created.
The text was updated successfully, but these errors were encountered: