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
When the disk recovering to is full for example, rear does not inform the user about this "soft" tar-error. tar runs through the whole archive with errors. Everything looks fine until you boot your system. Only when there are necessary files missing for restoring the bootloader for example, then you see errors that are related to these functions, not that the disk is full.
The text was updated successfully, but these errors were encountered:
No, there is no error in the logfile. And also not on the screen. I remember now, the error was visible in the logfile where tar writes its verbose out to. I'll have to get this. I will run the test again...
When the disk recovering to is full for example, rear does not inform the user about this "soft" tar-error. tar runs through the whole archive with errors. Everything looks fine until you boot your system. Only when there are necessary files missing for restoring the bootloader for example, then you see errors that are related to these functions, not that the disk is full.
The text was updated successfully, but these errors were encountered: