* Kern Sibbald schrieb am 16.09.07 um 20:59 Uhr: > Hello, Hi Kern,
> > It appears that it is dying on the posix_fadvise() OS call. The call is in > <bacula-source>/src/lib/bsock.c at line 492. All the arguments to the call > are valid, so, it would appear that something in the posix_fadvise() call > (the OS I think) is broken. > > You can test this theory by disabling the posix_fadvise() call by putting // > at the beginning of the line and rebuilding. > > You might also want to disable the posix_advise() calls in > src/findlib/bfile.c > (2 of them) and in src/stored/spool.c (one). > > You can disable them all *after* doing a ./configure, by editing src/config.h > and commenting out the #define HAV_POSIX_FADVISE line. > > Actually the crash is happening at the beginning of despooling attribute data. > Bingo! I just commented out the "#define HAV_POSIX_FADVISE" line, recompiled... No more crashes. May this behavior depend on the kernel? The server running bacula is a debian sarge system, but it is running an older kernel (2.4.20) than what is in sarge because of a special kernel-module. So my question is: is posix_fadvise() in sarge bad or is it my combination of sarge supporting it and that kernel 2.4.20 maybe not supporting it? Thanks for helping! -Marc > Regards, > > Kern > -- **************************************************** * (morganj): 0 is false and 1 is true, correct? * * (alec_eso): 1, morganj * * (morganj): bastard. * ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
