On Fri, Feb 24, 2006 at 10:12:33AM +0100, Kern Sibbald wrote: > On Friday 24 February 2006 04:28, Ross Boylan wrote: > > On Thu, Feb 23, 2006 at 12:06:12PM +0100, Arno Lehmann wrote: > > > Hello, > > > > > > On 2/23/2006 8:19 AM, Ross Boylan wrote: > > > >I got the error in the subject line while doing backups. I'm running > > > > ... > > > > > >Here's more of the logs: > > > >22-Feb 02:21 wheat-dir: Start Backup JobId 963, > > > > Job=MSD.2006-02-22_01.05.03 22-Feb 02:21 wheat-sd: Volume > > > > "Inc2006-02-22_0197" previously written, moving to end of data. > > > >22-Feb 02:22 wheat-sd: End of Volume "Inc2006-02-22_0197" at 0:312 on > > > >device /var/spool/bacula. Write of 64512 bytes got 45209. > > > > > > Here, only part of a block could be written, and... > > > > Yes, that does look as if the partition really ran out of room. > > > > .... > > > > > >22-Feb 02:22 wheat-dir: MSD.2006-02-22_01.05.03 Error: sql_update.c:327 > > > >sql_update.c:327 update UPDATE Media SET > > > >VolJobs=0,VolFiles=0,VolBlocks=0,VolBytes=0,VolMounts=0,VolErrors=0,VolW > > > >rites=1,MaxVolBytes=681574400,LastWritten='2006-02-22 > > > > 02:22:39',VolStatus='',Slot=0,InChanger=0,VolReadTime=0,VolWriteTime=0 > > > > WHERE VolumeName='Inc2006-02-22_0198' failed: ERROR: new row for > > > > relation "media" violates check constraint > > > >"media_volstatus" > > > > > > > >22-Feb 02:22 wheat-dir: MSD.2006-02-22_01.05.03 Error: Catalog error > > > >updating Media record. sql_update.c:327 update UPDATE Media SET > > > >VolJobs=0,VolFiles=0,VolBlocks=0,VolBytes=0,VolMounts=0,VolErrors=0,VolW > > > >rites=1,MaxVolBytes=681574400,LastWritten='2006-02-22 > > > > 02:22:39',VolStatus='',Slot=0,InChanger=0,VolReadTime=0,VolWriteTime=0 > > > > WHERE VolumeName='Inc2006-02-22_0198' failed: > > > > > > Trying to insert an empty string for VolStatus might be a bug. > > > > > > I'd report this as a bug. > > > > You mean in bacula, or postgres? > > > > So the problem might be that when the write fails, bacula tries to > > record an illegal VolStatus? > > What version of Bacula are you using. This was a problem with 1.36 but should > not occur on 1.38.x
1.36, so I guess the problem is already fixed. Yay! > > In any case, I don't consider this a serious bug because if your disk is > full, > pretty much everything is going to break. Agreed. > > How many times did this error repeat? If it was more than 5 or 10, then there > is a bug that I would like to fix since Bacula should terminate the job on a > fatal database update ... though certain database update failures are not > considered fatal ... My original message has fuller logs, but I think I saw the error only 2 or 3 times. At any rate, 2 or 3 jobs ran after the original failure. I suppose it may have started them earlier: all the jobs were scheduled to run at once, with different priorities. I have a one job at a time configuration. Ross ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
