Hello,
11.06.2008 11:38, Thomas wrote:
> Hi List,
>
> today i noticed that bacula 2.4.0 gets confused with two autochangers.
>
> I have one Director and two Storage-Daemons on two hosts,
> and each Storage-Daemon has a autochanger with two SDLT-Drives attached.
>
> from the logfile:
>
> 2008-06-11 08:48:43backup-sd-bb JobId 44612: End of Volume "INC021" at
> 426:4371 on device "JBBB-1" (/dev/nst0). Write of 64512 bytes got -1.
> 2008-06-11 08:48:47backup-sd-bb JobId 44612: Re-read of last block succeeded.
> 2008-06-11 08:48:47backup-sd-bb JobId 44612: End of medium on Volume "INC021"
> Bytes=395,479,010,304 Blocks=6,130,316 at 11-Jun-2008 08:48.
> 2008-06-11 08:48:47backup-sd-bb JobId 44612: 3307 Issuing autochanger "unload
> slot 15, drive 0" command.
> 2008-06-11 08:49:36backup-dir JobId 44612: There are no more Jobs associated
> with Volume "INC031". Marking it purged.
> 2008-06-11 08:49:36backup-dir JobId 44612: All records pruned from Volume
> "INC031"; marking it "Purged"
> 2008-06-11 08:49:36backup-dir JobId 44612: Recycled volume "INC031"
> 2008-06-11 08:49:36backup-sd-bb JobId 44612: 3301 Issuing autochanger
> "loaded? drive 0" command.
> 2008-06-11 08:49:36backup-sd-bb JobId 44612: 3302 Autochanger "loaded? drive
> 0", result: nothing loaded.
> 2008-06-11 08:49:36backup-sd-bb JobId 44612: 3304 Issuing autochanger "load
> slot 16, drive 0" command.
> 2008-06-11 08:49:55backup-sd-bb JobId 44612: 3305 Autochanger "load slot 16,
> drive 0", status is OK.
> 2008-06-11 08:50:05backup-sd-bb JobId 44612: Recycled volume "INC022" on
> device "JBBB-1" (/dev/nst0), all previous data lost.
> 2008-06-11 08:50:05backup-sd-bb JobId 44612: New volume "INC022" mounted on
> device "JBBB-1" (/dev/nst0) at 11-Jun-2008 08:50.
>
>
>
> Volume INC021 is in Jukebox JBBB.
> JBBB is the configured Storage for this Job.
>
> Volume INC031 is in the Jukebox JBGS in Slot 16
> and it is the oldest available Volume for the Pool INC.
> Bacula recycled the oldest Volume (INC031)
> and then it loads Slot 16 from the Jukebox JBBB
> and recycles also Volume INC022.
>
>
> Volume INC022 was last written 9 days ago:
>
> 2008-06-02 00:36:16backup-sd-bb JobId 43915: End of Volume "INC022" at
> 398:4686 on device "JBBB-2" (/dev/nst1). Write of 64512 bytes got -1.
>
> but the Volume Retention is 21 days, so this should not happen.
If you verified the retention period hasn't expired I'd say this
definitely is a bug.
> => Bacula has recycled the oldest Volume from the Pool,
> but in the wrong Storage for the Job. After that it loads
> the same Slot from the correct Storage and recycles this Volume
> too, without taking care of the retention periods.
This might have to do with having the same Media Type for volumes in
different storage devices - still it shouldn't happen.
>
> I'm running this setup since ~2 years with all released Bacula versions since
> 1.38,
> and i never see that before, so i think it is a bug.
It might even be two bugs, though it's hard to tell without further
testing and more information.
I suggest reporting this at bugs.bacula.org.
Arno
>
> Regards
>
> Thomas
>
--
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|