Hi Bill, see below > On 19. Apr 2023, at 17:22, Bill Arlofski via Bacula-users > <bacula-users@lists.sourceforge.net> wrote: > > On 4/19/23 03:52, Justin Case wrote: >> For the sake of completeness: I have read in the document “Community Disk >> Backup Design” in section 3.1 that it is possible what you are proposing and >> how to do it and implemented it, but it is not working the way one would >> expect (see my other mail a few minutes ago). > > Hello Justin, > > > This message does not indicate to me a problem with a drive being in use, but > rather this volume cannot be truncated because it is reserved by a job. > > ----8<---- > 3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume > “pool1-vol-0599", because it is reserved by someone else. > ----8<---- >
You need to look a two lines together: Error truncating Volume “pool1-incr-vol-1109" 3908 Error reserving volume: vol_mgr.c:418 Cannot free Volume “pool2-full-vol-0703", because it is reserved by someone else. This seems to say that pool1-incr-vol-1109 couldn’t be mounted to be truncated because pool2-full-vol-0703 is still mounted, and it cannot be unmounted as it is stil used by a backup job. To me this makes some sense. > Let me check something too... In other operations (like label), you can > specify the disk device to use. I think I recall this not being the case with > the truncate command, and that it always uses the first drive in the > autochanger. Well, if this is true, its a problem, as the first drive is busy with the backup job. > I will ask my colleagues if they remember this issue in the Enterprise > version and if it was address/modified/fixed. > > Be right back. :) OK waiting :)
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
