Re: [Vchanger-users] Again wrong media and volume on error.../2

[Josh F. <jf...@ja...>]

See my previous post. I believe the update slots is not happening after 
the disk is ejected and BEFORE the job is run.

Also, the below SQL can be put it your query.sql file to define a menu 
item for the bconsole query command that will list volumes that bacula 
thinks are in a slot (or "in changer").

# 15
:List Volumes Bacula thinks are in changer
SELECT MediaId,VolumeName,VolBytes/(1024*1024*1024) AS GB,Storage.Name
   AS Storage,Slot,Pool.Name AS Pool,MediaType,VolStatus
   FROM Media,Pool,Storage
   WHERE Media.PoolId=Pool.PoolId
   AND Slot>0 AND InChanger=1
   AND Media.StorageId=Storage.StorageId
   ORDER BY MediaType ASC, Slot ASC;

It can be useful to see if bacula thinks the correct volumes are in slots.


On 5/8/23 05:44, Marco Gaiarin wrote:
> I've tried to restart SD, cleanup all jobs and start from a fresh condition.
>
> Nope. Still bacula try to mount volume in the wrong media, not in slots,
> putting all volumes on error.
>
>
> So the 'virtual changer' metaphore seems to work until you don't have a
> purged media in a non-mounted set, because bacula insist to mount it,
> putting it on error.
> I've tried to google around a bit, but found only some old reminescent post
> on bugs of bacula 1.XX i hope solved now. ;-)
>
>
> What i'm missing?! Thanks.
>