>>>>> On Mon, 19 Nov 2007 22:24:35 -0600, Craig Dupree said: > > Hi Everyone, > > Below is a set of messages from a backup I was running tonight. For this > set of fulls, I turned on data spooling. Mostly it's been going okay > until I ran this last job and got this: > > 19-Nov 17:05 hippo-sd JobId 389: Spooling data ... > ccbbweb2-fd: /var/www/vhosts/dogma is a different filesystem. Will not > +descend from /var/www/vhosts into /var/www/vhosts/dogma > 19-Nov 17:57 hippo-sd JobId 389: User specified spool size reached. > 19-Nov 17:57 hippo-sd JobId 389: Writing spooled data to Volume. Despooling > +5,368,717,234 bytes ... > 19-Nov 17:59 hippo-sd JobId 389: Despooling elapsed time = 00:01:10, Transfer > +rate = 76.69 M bytes/second > 19-Nov 17:59 hippo-sd JobId 389: Spooling data again ... > 19-Nov 18:15 hippo-sd JobId 389: Job write elapsed time = 01:10:56, Transfer > +rate = 1.873 M bytes/second > 19-Nov 18:15 hippo-sd JobId 389: Committing spooled data to Volume "000025". > +Despooling 2,646,803,480 bytes ... > 19-Nov 18:15 hippo-sd JobId 389: Fatal error: Cannot write block. Device at > EOM. > 19-Nov 18:15 hippo-sd JobId 389: Fatal error: spool.c:294 Fatal append error > on > +device "Drive-1" (/dev/nst0): ERR= > 19-Nov 18:15 hippo-sd JobId 389: Despooling elapsed time = 00:00:01, Transfer > +rate = 2.646 G bytes/second > 19-Nov 18:15 hippo-dir JobId 389: Error: Bacula hippo-dir 2.2.5 (09Oct07): > +19-Nov-2007 18:15:59 > > Is spooling incompatible with having the storage daemon request and/or use > another tape?
Spooling should work fine with this. Have you run the btape 'fill' test successfully with this configuration? > Interestingly enough after the next back up started I got > error messages along the lines of the number of files not mismatching on > same tape (so that it was still marked as being appendable?) > > This is with bacula 2.2.5 (both director and storage daemon). The clients > are still various levels. I've checked the patches for 2.2.6, and > also checked back through my archives of the mailing lists. I don't > see this error specifically, though it seems like I should have. Oh, > lets see. The drive is a new LTO3 installed in an older Dell PV-132T. > It's worked flawlessly for a couple of weeks now, until a tape didn't > eject properly. Is that the error above or some other problem with the tape not ejecting properly? Have non-spooled multitape backups worked 100%? __Martin ------------------------------------------------------------------------- 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-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
