Big bug: cronopete move home folder to another name #52
Comments
What????????? That makes no sense... Which backend are you using? |
That what I think first, but I can ensure you that happens, when cronopete start it process... I was a big afraid. |
No, no... which backend, in cronopete. Are you using the default rsync backend for an external hard disk, or are you using the backend for storing the backups in a folder? |
Does it happens always, or only once? |
only once, this afternoon.
I have used cronopete since one year, and it didn't happens in the past
|
And which backend, in cronopete. Are you using the default rsync backend for an external hard disk, or are you using the backend for storing the backups in a folder? |
to store in an external disk. |
I will check all the places where I rename folders... but it is very odd... |
yeah... |
I use cronopete 4.4.0 |
Please, update to version 4.6.0. |
done
|
Ok. It fixes a problem when there are blank spaces. Just in case. Anyway, I'm checking the code. |
thanks. No space in my disk name. |
Yes, but the bug triggered by that could also be triggered by other "odd elements", so just to be sure... |
same problem today. Maybe the problem happens when the external hard disk is disconnected for any reason when processing to the backup. |
Hi,
just some minutes ago, it happens a strange thing.
Cronopete start it backup. But instead of rsync
/home/username
to the backup device, it move it to/home/2018_10_01_18:12:34:15384135
.Consequently : not any program was able to find its file. I created in emergency an user, restart, and opening session of this user, I see tha
t the files was kept (cf screenshot).
The text was updated successfully, but these errors were encountered: