On Tuesday 03 May 2005 03:51, Jeffery P. Humes wrote:
> Any ideas why I would get this error?
>
>
>
> 02-May 20:33 kninfratemp-sd: mycastleapp01.2005-05-01_01.05.01 Fatal
> error: spool.c:315 Spool block too big. Max 64512 bytes, got 909259313
>
> This error seems to happen when full backups happen.
Your spool file got clobbered.
Possible reasons (hard to be specific when you didn't supply any basic info):
1. You are running two Storage daemons and pointing them to the same working
directory.
2. The partition on which your spool file resides has filled, and your OS (not
specified) doesn't return the correct error code during writing.
3. Failing hard disk.
4. Some other process writing into the spool file.
5. Some strange bug in Bacula with multiple jobs or improper Device
specification.
6. A 32/64 bit configuration problem with Bacula on your OS
-- very bad if this is true.
Try setting your max spool file size to 1.5GB (not a really good solution).
Run btape. If it complains on startup about 32/64 bits off_t, you have
problems that you should resolve in the Bacula build.
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
