Arno Lehmann schrieb: > >> [snip] > >> Job #1: > >> > >> 08-Apr 00:05 VU0EM005: BeforeJob: run command "/usr/bin/ssh [snip]" > >> 08-Apr 00:07 VU0EM005: Start Backup JobId 121, > >> Job=SMTCZB0003.2007-04-08_00.05.00 > >> 08-Apr 00:08 VU0EM005: 3307 Issuing autochanger "unload slot 4, drive 0" > >> command. > >> 08-Apr 00:09 VU0EM005: 3304 Issuing autochanger "load slot 5, drive 0" > >> command. > >> 08-Apr 00:10 VU0EM005: 3305 Autochanger "load slot 5, drive 0", status is > >> OK. > >> 08-Apr 00:10 VU0EM005: 3301 Issuing autochanger "loaded? drive 0" command. > >> 08-Apr 00:10 VU0EM005: 3302 Autochanger "loaded? drive 0", result is Slot > >> 5. > >> 08-Apr 00:10 VU0EM005: Recycled volume "06D124L3" on device "LTO3" > >> (/dev/nst0), all previous data lost. > >> > >> That's fine, I expected volume 06D124L3 to be overwritten at this time. > >> > >> 08-Apr 00:10 VU0EM005: Max configured use duration exceeded. Marking > >> Volume "06D124L3" as Used. > >> > >> But I don't know what happend at this point. Why does bacula mark volume > >> 06D124L3 as used right after the job started. The configured duration time > >> is 4 days, I checked this. > >> > >> 08-Apr 00:10 VU0EM005: Spooling data ... > >> SMTCZB0003-fd: Filesystem change prohibited. Will not descend into > >> /var/lib/nfs/rpc_pipefs > >> SMTCZB0003-fd: Filesystem change prohibited. Will not descend into > >> /dev > >> SMTCZB0003-fd: Filesystem change prohibited. Will not descend into > >> /sys > >> SMTCZB0003-fd: Filesystem change prohibited. Will not descend into > >> /boot > >> 08-Apr 00:12 VU0EM005: Job write elapsed time = 00:02:23, Transfer rate = > >> 6.766 M bytes/second > >> 08-Apr 00:12 VU0EM005: Committing spooled data to Volume "06D124L3". > >> Despooling 968,636,754 bytes ... > >> 08-Apr 00:12 VU0EM005: Despooling elapsed time = 00:00:07, Transfer rate = > >> 138.3 M bytes/second > >> 08-Apr 00:12 VU0EM005: Sending spooled attrs to the Director. Despooling > >> 1,543,784 bytes ... > >> 08-Apr 00:12 VU0EM005: AfterJob: run command "/usr/bin/ssh [snip]" > > [snip] > > > > Nobody? > > Looks like that...
Hey, you're not nobody ;) > > I'm a bit lost, > > So am I. I checked your probelm description, and I don't see anything > obvious. I didn't expect anything simple, to be fair :-) Thanks. > The one thing I would do in your situation is - observe things. If this > repeats, I would try to get catalog data whenever a job starts, perhaps > even a dump of the Media table or something... just so you have some > data to look at. After the error has occured, it's likely Bacula > modified the catalog entries. Well, I've a backup of the bacula database from last weeks full backup (2007-04-01). This shows the same value for voluseduration, 345600 (4 days). COPY media (mediaid, volumename, slot, poolid, mediatype, mediatypeid, labeltype, firstwritten, lastwritten, labeldate, voljobs, volfiles, volblocks, volmounts, volbytes, volparts, volerrors, volwrites, volcapacitybytes, volstatus, enabled, recycle, volretention, voluseduration, maxvoljobs, maxvolfiles, maxvolbytes, inchanger, storageid, deviceid, mediaaddressing, volreadtime, volwritetime, endfile, endblock, locationid, recyclecount, initialwrite, scratchpoolid, recyclepoolid, "comment") FROM stdin; 5 06D124L3 5 5 LTO3 0 0 2007-02-24 23:45:04 2007-02-25 11:04:06 2007-02-24 23:45:04 3 16 230427 1 14865371136 0 0 230428 0 Recycle 1 1 2678400 345600 0 0 0 1 2 0 0 0 0 15 2014 0 0 \N 0 0 \N Because recycling and marking of the volume happend after the job started (at the same minute 00:10), I've no idea if it would make sense to dump the db in a run before skript before every backup. > > my old bacula install worked as expected with > > a similar config, so I don't think that I configured bacula-dir wrong. > > This new install worked for the last 3 months, other volumes were > > recycled and reused as expected. > > > > What could lead to a volume that is recycled and then marked as used > > just a couple of seconds afterwards? I double checked, the volume use > > duration of this volume is set to 4 days. > > Ok, double-checking is always valuable :-) I found the message "Max > configured..." only once in the source, so it's safe to assume the > message is not used out of context. Ok. > A look at the source dosn't reveal anything extraordinary, at east to > me. Unless you asume that the catalog data and the current system time > might be messed up... is your system time correct, does your catalog > know about the time zone, and whatever esle might be important? I'm using an ntp server, so date and time is ok. The syslog doesn't show anything unusual at the time it happend. bacula=> select current_timestamp; now ------------------------------- 2007-04-11 08:38:28.697112+02 (1 Zeile) bacula=> show timezone; TimeZone --------------- Europe/Berlin (1 Zeile) At them moment I would consider this as a bug, but I would like to here Kern's opinion on this before I open a bug report. Ralf ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users