Hi all I have bacula 2.2/postgresql running on a Centos4/i386; working with a SD from bacula 2.4 on a Centos5/x86_64. On the second box (x86_64) I have a 160 GB FileStorage space.
Now bacula fails from time to time with these messages (upon termination of a job): 05-Dez 01:15 esf2-dir: esf3-snapshot.2008-12-05_01.05.01 Error: sql_create.c:154 sql_create.c:154 update UPDATE Media SET EndFile=0, EndBlock=3014671511 WHERE MediaId=282 failed: (...) Obviously the EndBlock is too large for putting into a regular 32bit integer database field. Changing the type to bigint in the database seemed to solve the problem for me. Is this a known deficiency? Should the declaration for EndBlock be changed from integer to bigint in a future database schema version? My schema is version 10. Regards --Marcel ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
