I spotted that while looking at the live logs, seems rather odd as theses files surely didn’t changed. since about 10 years.
2.2.0 beta client
2.2.1 beta server
parallel hash enabled
i Still didn’t had any crash on the server, it s still running through gdb.
Posting a few warning here, but actually there’s quite a lot of them.
I wonder if that comes from the fact that i first added the /home as a folder to backup, then started the backup.
Then changed my mind, and removed it from the client to add /home as a subclient… I Then tried to stop the backup on the main client as i noticed files were uploaded 2 times.
Now i wonder if the files are not being mixed up or something when they re written at the destination.
Also when i stop the backup it always resume so i let it continue. But i wonder if it s not causing some issues.
06/03/17 19:20 WARNING Client calculated hash of “/data/urbackup2/pascalou/170603-1859/various/photos/RawCameraPhotos/2007 06/04turin/dscn2881.jpg” differs from server calculated hash. The file is being backed up without a snapshot so this is most likely caused by the file changing during the backup. The backed up file may be corrupt and not a valid, consistent backup. (Hash: tree-sparse)
06/03/17 19:20 WARNING Client calculated hash of “/data/urbackup2/pascalou/170603-1859/various/photos/RawCameraPhotos/2007 06/05retour/dscn3263.jpg” differs from server calculated hash. The file is being backed up without a snapshot so this is most likely caused by the file changing during the backup. The backed up file may be corrupt and not a valid, consistent backup. (Hash: tree-sparse)
06/03/17 19:20 WARNING Client calculated hash of “/data/urbackup2/pascalou/170603-1859/various/photos/RawCameraPhotos/2007 06/05retour/dscn3313.jpg” differs from server calculated hash. The file is being backed up without a snapshot so this is most likely caused by the file changing during the backup. The backed up file may be corrupt and not a valid, consistent backup. (Hash: tree-sparse)
06/03/17 19:29 WARNING Client calculated hash of “/data/urbackup2/pascalou/170603-1859/home_orogor/Desktop/compat-drivers-2013-03-04-u/compat-drivers-2013-03-04-u/compat-drivers-2013-03-04-u/drivers/ssb/sdio.c” differs from server calculated hash. The file is being backed up without a snapshot so this is most likely caused by the file changing during the backup. The backed up file may be corrupt and not a valid, consistent backup. (Hash: tree-sparse)
06/03/17 19:29 DEBUG HT: Linked file: “/data/urbackup2/pascalou/170603-1859/home_orogor/Desktop/compat-drivers-2013-03-04-u/compat-drivers-2013-03-04-u/compat-drivers-2013-03-04-u/drivers/ssb/scan.c”
1859/home_orogor/Desktop/compat-drivers-2013-03-04-u/compat-drivers-2013-03-04-u/compat-drivers-2013-03-04-u/drivers/ssb/sprom.c" differs from server calculated hash. The file is being backed up without a snapshot so this is most likely caused by the file changing during the backup. The backed up file may be corrupt and not a valid, consistent backup. (Hash: tree-sparse)
06/03/17 19:29 DEBUG PT: Hashing file “Makefile”
06/03/17 19:29 WARNING Client calculated hash of “/data/urbackup2/pascalou/170603-1859/home_orogor/Desktop/compat-drivers-2013-03-04-u/compat-drivers-2013-03-04-u/compat-drivers-2013-03-04-u/drivers/video/Makefile” differs from server calculated hash. The file is being backed up without a snapshot so this is most likely caused by the file changing during the backup. The backed up file may be corrupt and not a valid, consistent backup. (Hash: tree-sparse)