On Wednesday 13 September 2006 11:30, Alan Brown wrote: > On Tue, 12 Sep 2006, Kern Sibbald wrote: > > > On Tuesday 12 September 2006 18:21, [EMAIL PROTECTED] wrote: > >> I'm running into a frequent situation where Bacula wants a given volume to > > be > >> in one drive of our autochanger, and it doesn't seem to find the volume when > >> it's already in the other drive. > >> > >> This is with Bacula 1.38.9, under Linux (FC1), with a 23-slot, 2 drive > >> autochanger and mysql5. > >> > >> Most backups work fine, but this is a persistent problem. > > > > Two drive autochangers did not work correctly until Bacula version 1.38.11, > > and there have been no such problems posted against 1.38.11. > > > Kern: This is exactly the problem I posted last week and I am running 1.38.11
I don't think it is the same problem, but that is not important. What is important is he is not using 1.38.11, and there are known problems with the management of Volume names on prior versions, so the problem is no longer relevant to me -- I cannot support old versions other than the most recent one. > > I know why it's occuring - people are running update slots against a > particular tape drive instead of the autochanger > > And I know why they do that - running update slots against the changer > only ever unloads drive 0, no matter which drive is actually specified. > > > I know you don't regard it as a bug that when run this way, all the tapes > in the changer end up associated with an individual drive, but I do. I'm not planning to change the current behavior, but I can make sure that the document is explicit enough on this point. > > Additionally it's definitely a bug that update slots ignores any drive > specfication. > > IE: > > *update slots > The defined Storage resources are: > 1: File > 2: MSL6000-changer > 3: MSL6000-0 > 4: MSL6000-1 > 5: DVD > Select Storage resource (1-5): 2 > Enter autochanger drive[0]: 1 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Connecting to Storage daemon MSL6000-changer at msslay.mssl.ucl.ac.uk:9103 > ... > 3306 Issuing autochanger "slots" command. > Device "MSL6000-changer" has 60 slots. > Connecting to Storage daemon MSL6000-changer at msslay.mssl.ucl.ac.uk:9103 > ... > 3301 Issuing autochanger "loaded drive 0" command. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^This is not drive 1 > 3302 Autochanger "loaded drive 0", result is Slot 47. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^This is not drive 1 > 3307 Issuing autochanger "unload slot 47, drive 0" command. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^This is not drive 1 I wasn't aware of this problem with the drive number, and I don't remember anyone mentioning it before. Thanks for pointing it out. The big question is whether or not this problem exists in 1.39.22 or not, because it is unlikely that I will be making any further patches for 1.38.11. > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
