Am Dienstag, den 25.07.2017, 13:12 +0200 schrieb Bruno Friedmann: > > On July 24, 2017 8:39:48 PM GMT+02:00, "Tomas Martišius" <tomas.puga. > [email protected]> wrote: > > > > 2017 m. liepa 24 d., pirmadienis 19:25:20 UTC+3, Tom Weber rašė: > > > > > > Am Montag, den 24.07.2017, 08:58 -0700 schrieb Tomas Martišius: > > > > > > > > > > > > May be you find solution for this problem? > > > actually I'm rather disappointed that none of the developers > > > seems to > > > care about such a severe bug. > Did you open a bug report in appropriate place ? > Personaly I didn't see a number reported here
I did ask on the list first if this is a known problem or not (at that time I didn't know / hadn't realized there was bugs.bareos.org). A report about corrupted backups with a backup software that triggers no reaction at all from the developers makes me feel really strange. If the provided info isn't good enough or if this list is the wrong place to report - a little pointer would have helped. So either they don't read here or don't care. And yes, maybe I could have reported more completely and via bugtracking etc. But my priority was a) to inform the community that there is a serious problem and b) to get my s***t here working again after a needed bareos backup seriously failed on me. So sorry for not spending 2 more days making a perfectly fine and well formated bug report. > > > > > > like 30 minutes ago I might have found something. > > > > > > do you happen to have > > > signature = SHA1 > > > in your fileset definition? > > > > Still it was not clear to me from where you pick your binaries. "A couple of weeks ago I upgraded a fileserver to debian 9 with the included filedaemon 16.2.4-3." "Today I had to figure that after a restore of the debian 9 (bareos 16.2.4 filedaemon) client all restored files are corrupt!" For me that sounds clear that I was talking about the debian 9 provided filedaemon. > > > change this to MD5 and try again. > > > > > > Tom > btw I never seem this kind of trouble (I'm using openSUSE as os) > > > > > Thanks for solution. With MD5 it seems all works right. But trust > > in > > the project has fallen. > > > > Best regards, > > > > Tomas > sha1 or md5 are used for checksum calculation. I don't think they > have something to do with internal content of files. I can reproduce file corruption (always the same) with SHA1 which doesn't happen with MD5. That took me quite some time to figure because i couldn't believe it had something to do with my problem either. Bug is filed in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869608 Tom -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
