Arno:

I thought it was curious too.  I was certain that Dan's fix was what I needed.  
I checked to see that endblock was now defined as bigint:

bacula=# \d jobmedia
                                 Table "public.jobmedia"
   Column   |  Type   |                            Modifiers                    
         
------------+---------+------------------------------------------------------------------
 jobmediaid | integer | not null default 
nextval('public.jobmedia_jobmediaid_seq'::text)
 jobid      | integer | not null
 mediaid    | integer | not null
 firstindex | integer | not null default 0
 lastindex  | integer | not null default 0
 startfile  | integer | not null default 0
 endfile    | integer | not null default 0
 volindex   | integer | not null default 0
 startblock | bigint  | not null default 0
 endblock   | bigint  | not null default 0
Indexes:
    "jobmedia_pkey" primary key, btree (jobmediaid)
    "job_media_job_id_media_id_idx" btree (jobid, mediaid)

I have implemented "Maximum Volume Bytes = 2000000000" in the Pool record of 
the director configuration file.  I think that is an acceptable work-around.

Thanks,
Anthony Dodson

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Arno
Lehmann
Sent: Wednesday, October 19, 2005 3:10 PM
To: Anthony Dodson
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Jobmedia error: integer out of range


Hello,

On 19.10.2005 20:07, Anthony Dodson wrote:

> 19-Oct 13:37 macaroni-dir: LoonAll.2005-10-19_13.27.38 Error: 
> sql_create.c:141 sql_create.c:141 update UPDATE Media SET EndFile=0, 
> EndBlock=2999743393 WHERE MediaId=203 failed:
> ERROR:  integer out of range
...
> I tried the table modifications for startblock and endblock as bigint from 
> Dan Languille found here: 
> http://thread.gmane.org/gmane.comp.sysutils.backup.bacula.general/4932 but 
> that did not seem to help.  This is the first file media for me that has went 
> over 2GB.

Well, I suppose that the simplest solution would be to limit the volumes 
to a size safely below the 2GB limit. But I wonder that Dan's 
modification was not helpful - as far as I understand that *should* fix 
it. Have you checked how the columns are defined in the catalog?


Arno

-- 
IT-Service Lehmann                    [EMAIL PROTECTED]
Arno Lehmann                  http://www.its-lehmann.de


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


IMPORTANT WARNING:
This e-mail is intended for the use of the person to whom it is addressed and 
may contain information that is privileged and confidential, the disclosure of 
which is governed by applicable law. Dissemination, distribution or copying of 
this information in an unauthorized manner is strictly prohibited. Sender 
accepts no liability for any damage caused by any virus transmitted by this 
e-mail. If you receive this in error, please notify the sender.
==============================================================================



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to