You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
using "smart remove" together with the settings "if free space less than" (resp. "if free inodes less than") might lead to (probably) unintended behavior as BiT would remove the oldest snapshot if the space / inodes threshold is reached no matter what is defined for smart remove.
Instead of having the oldest snapshot deleted the user might want to adjust the smart remove settings.
Suggestions:
show a warning when the user enables both settings at the same time or
disallow to enable both features at the same time
If you think about the settings, BiT's current behavior makes sense ideed, however, it might not be that intuitive. BiT should make sure that the user completely understands when a snapshot is deleted (as this is crucial for a backup tool).
Best regards,
kroka
The text was updated successfully, but these errors were encountered:
Maybe you want to join the discussion. We need suggestions about how the Auto-remove dialog should look like to make the behavior clear to the users.
You suggested an extra warning dialog. I don't like an message box. Maybe a red colored text label appearing in the dialog if both options are enabled?
Hi,
using "smart remove" together with the settings "if free space less than" (resp. "if free inodes less than") might lead to (probably) unintended behavior as BiT would remove the oldest snapshot if the space / inodes threshold is reached no matter what is defined for smart remove.
Instead of having the oldest snapshot deleted the user might want to adjust the smart remove settings.
Suggestions:
If you think about the settings, BiT's current behavior makes sense ideed, however, it might not be that intuitive. BiT should make sure that the user completely understands when a snapshot is deleted (as this is crucial for a backup tool).
Best regards,
kroka
The text was updated successfully, but these errors were encountered: