Hi Josh,
On Tue, May 10, 2016 at 11:00 PM, Josh Fisher <jfis...@pvct.com> wrote:
> Hi Pann,
>
> This is almost certainly the vchanger race condition bug that I mentioned
> previously. The bconsole output in the vchanger log tells me that bconsole
> is being invoked by vchanger to label the volumes. Put a bconsole='' line
> in vchanger.conf and try running the label barcodes command from bconsole.
>
I did what you asked me to try. I changed the line
bconsole="/usr/sbin/vconsole" to bconsole="" in vchanger.conf. Then run
the lable barcode command in bconsole
On 5/10/2016 8:26 AM, Pann Tolk wrote:
>
> Hi Guys,
>
> I'm making a second attempt to setup Bacula 7.4.0 with vchanger 1.0.1.
> This time, instead of installing Bacula on Fedora 23, I used Centos 7.2.
>
> I followed the vchangerHowto.html to configure vchanger. When I run the
> command to create the volumes:
>
> [root@deneb vchanger]# vchanger /etc/vchanger/vchanger01.conf createvols
> 0 18
> creating label 'vchanger01_0_0'
> creating label 'vchanger01_0_1'
> creating label 'vchanger01_0_2'
> creating label 'vchanger01_0_3'
> creating label 'vchanger01_0_4'
> creating label 'vchanger01_0_5'
> creating label 'vchanger01_0_6'
> creating label 'vchanger01_0_7'
> creating label 'vchanger01_0_8'
> creating label 'vchanger01_0_9'
> creating label 'vchanger01_0_10'
> creating label 'vchanger01_0_11'
> creating label 'vchanger01_0_12'
> creating label 'vchanger01_0_13'
> creating label 'vchanger01_0_14'
> creating label 'vchanger01_0_15'
> creating label 'vchanger01_0_16'
> creating label 'vchanger01_0_17'
> Created 18 volume files on magazine 0
>
>
> It appears that the volumes are successfully created:
>
> [root@deneb vchanger]# ls -l
> /mnt/vchanger/1fde15be-83a4-4b67-accc-378d5fa10ea7/
> total 16
> drwxr-x--- 2 root root 16384 Apr 27 13:57 lost+found
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_0
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_1
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_10
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_11
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_12
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_13
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_14
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_15
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_16
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_17
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_2
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_3
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_4
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_5
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_6
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_7
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_8
> -rw-r--r-- 1 bacula tape 0 May 10 17:35 vchanger01_0_9
> [root@deneb vchanger]#
>
>
> However, when I entered the following command, the output from bconsole
> shows that only the volume in the 1st slot has been added to the "Scratch"
> pool:
>
> [root@deneb vchanger]# echo "status slots storage=vchanger01 drive=0" |
> bconsole
> Connecting to Director deneb.pt.local:9101
> 1000 OK: 102 bacula-dir Version: 7.4.0 (16 January 2016)
> Enter a period to cancel a command.
> status slots storage=vchanger01 drive=0
> Automatically selected Catalog: MyCatalog
> Using Catalog "MyCatalog"
> Connecting to Storage daemon vchanger01 at deneb.pt.local:9103 ...
> 3306 Issuing autochanger "slots" command.
> Device "SATA-vchanger01" has 37 slots.
> Connecting to Storage daemon vchanger01 at deneb.pt.local:9103 ...
> 3306 Issuing autochanger "list" command.
> Slot | Volume Name | Status | Media Type |
> Pool |
>
> ------+------------------+-----------+----------------------+--------------------|
> 1 | vchanger01_0_0 | Append | File |
> Scratch |
> 2*| vchanger01_0_1 | ? | ?
> | ? |
> 3*| vchanger01_0_10 | ? | ?
> | ? |
> 4*| vchanger01_0_11 | ? | ?
> | ? |
> 5*| vchanger01_0_12 | ? | ?
> | ? |
> 6*| vchanger01_0_13 | ? | ?
> | ? |
> 7*| vchanger01_0_14 | ? | ?
> | ? |
> 8*| vchanger01_0_15 | ? | ?
> | ? |
> 9*| vchanger01_0_16 | ? | ?
> | ? |
> 10*| vchanger01_0_17 | ? | ?
> | ? |
> 11*| vchanger01_0_2 | ? | ?
> | ? |
> 12*| vchanger01_0_3 | ? | ?
> | ? |
> 13*| vchanger01_0_4 | ? | ?
> | ? |
> 14*| vchanger01_0_5 | ? | ?
> | ? |
> 15*| vchanger01_0_6 | ? | ?
> | ? |
> 16*| vchanger01_0_7 | ? | ?
> | ? |
> 17*| vchanger01_0_8 | ? | ?
> | ? |
> 18*| vchanger01_0_9 | ? | ?
> | ? |
> 19*| | ? | ?
> | ? |
> 20*| | ? | ?
> | ? |
> ...
> ...
> 37*| | ? | ?
> | ? |
> [root@deneb vchanger]#
>
> Following is taken from the vchanger log
>
> May 10 17:36:03: bconsole: output:
> Connecting to Director deneb.pt.local:9101
> 1000 OK: 102 bacula-dir Version: 7.4.0 (16 January 2016)
> Enter a period to cancel a command.
> label storage="vchanger01" pool="Scratch" barcodes
> Automatically selected Catalog: MyCatalog
> Using Catalog "MyCatalog"
> Connecting to Storage daemon vchanger01 at deneb.pt.local:9103 ...
> 3306 Issuing autochanger "slots" command.
> Device "SATA-vchanger01" has 37 slots.
> Connecting to Storage daemon vchanger01 at deneb.pt.local:9103 ...
> 3306 Issuing autochanger "list" command.
> The following Volumes will be labeled:
> Slot Volume
> ==============
> 1 vchanger01_0_0
> 2 vchanger01_0_1
> 3 vchanger01_0_10
> 4 vchanger01_0_11
> 5 vchanger01_0_12
> 6 vchanger01_0_13
> 7 vchanger01_0_14
> 8 vchanger01_0_15
> 9 vchanger01_0_16
> 10 vchanger01_0_17
> 11 vchanger01_0_2
> 12 vchanger01_0_3
> 13 vchanger01_0_4
> 14 vchanger01_0_5
> 15 vchanger01_0_6
> 16 vchanger01_0_7
> 17 vchanger01_0_8
> 18 vchanger01_0_9
> Do you want to label these Volumes? (yes|no): yes
> Connecting to Storage daemon vchanger01 at deneb.pt.local:9103 ...
> Sending label command for Volume "vchanger01_0_0" Slot 1 ...
> 3304 Issuing autochanger "load slot 1, drive 0" command for vol
> vchanger01_0_0.
> 3305 Autochanger "load slot 1, drive 0", status is OK for vol
> vchanger01_0_0.
> 3000 OK label. VolBytes=201 VolABytes=0 VolType=1 Volume="vchanger01_0_0"
> Device="SATA-vchanger01-drive-0" (/var/spool/vchanger/vchanger01/drive0)
> Catalog record for Volume "vchanger01_0_0", Slot 1 successfully created.
> Sending label command for Volume "vchanger01_0_1" Slot 2 ...
> 3307 Issuing autochanger "unload slot 1, drive 0" command for vol
> vchanger01_0_1.
> 3304 Issuing autochanger "load slot 2, drive 0" command for vol
> vchanger01_0_1.
> 3305 Autochanger "load slot 2, drive 0", status is OK for vol
> vchanger01_0_1.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_1.
> Sending label command for Volume "vchanger01_0_10" Slot 3 ...
> 3307 Issuing autochanger "unload slot 2, drive 0" command for vol
> vchanger01_0_10.
> 3304 Issuing autochanger "load slot 3, drive 0" command for vol
> vchanger01_0_10.
> 3305 Autochanger "load slot 3, drive 0", status is OK for vol
> vchanger01_0_10.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_10.
> Sending label command for Volume "vchanger01_0_11" Slot 4 ...
> 3307 Issuing autochanger "unload slot 3, drive 0" command for vol
> vchanger01_0_11.
> 3304 Issuing autochanger "load slot 4, drive 0" command for vol
> vchanger01_0_11.
> 3305 Autochanger "load slot 4, drive 0", status is OK for vol
> vchanger01_0_11.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_11.
> Sending label command for Volume "vchanger01_0_12" Slot 5 ...
> 3307 Issuing autochanger "unload slot 4, drive 0" command for vol
> vchanger01_0_12.
> 3304 Issuing autochanger "load slot 5, drive 0" command for vol
> vchanger01_0_12.
> 3305 Autochanger "load slot 5, drive 0", status is OK for vol
> vchanger01_0_12.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_12.
> Sending label command for Volume "vchanger01_0_13" Slot 6 ...
> 3307 Issuing autochanger "unload slot 5, drive 0" command for vol
> vchanger01_0_13.
> 3304 Issuing autochanger "load slot 6, drive 0" command for vol
> vchanger01_0_13.
> 3305 Autochanger "load slot 6, drive 0", status is OK for vol
> vchanger01_0_13.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_13.
> Sending label command for Volume "vchanger01_0_14" Slot 7 ...
> 3307 Issuing autochanger "unload slot 6, drive 0" command for vol
> vchanger01_0_14.
> 3304 Issuing autochanger "load slot 7, drive 0" command for vol
> vchanger01_0_14.
> 3305 Autochanger "load slot 7, drive 0", status is OK for vol
> vchanger01_0_14.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_14.
> Sending label command for Volume "vchanger01_0_15" Slot 8 ...
> 3307 Issuing autochanger "unload slot 7, drive 0" command for vol
> vchanger01_0_15.
> 3304 Issuing autochanger "load slot 8, drive 0" command for vol
> vchanger01_0_15.
> 3305 Autochanger "load slot 8, drive 0", status is OK for vol
> vchanger01_0_15.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_15.
> Sending label command for Volume "vchanger01_0_16" Slot 9 ...
> 3307 Issuing autochanger "unload slot 8, drive 0" command for vol
> vchanger01_0_16.
> 3304 Issuing autochanger "load slot 9, drive 0" command for vol
> vchanger01_0_16.
> 3305 Autochanger "load slot 9, drive 0", status is OK for vol
> vchanger01_0_16.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_16.
> Sending label command for Volume "vchanger01_0_17" Slot 10 ...
> 3307 Issuing autochanger "unload slot 9, drive 0" command for vol
> vchanger01_0_17.
> 3304 Issuing autochanger "load slot 10, drive 0" command for vol
> vchanger01_0_17.
> 3305 Autochanger "load slot 10, drive 0", status is OK for vol
> vchanger01_0_17.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_17.
> Sending label command for Volume "vchanger01_0_2" Slot 11 ...
> 3307 Issuing autochanger "unload slot 10, drive 0" command for vol
> vchanger01_0_2.
> 3304 Issuing autochanger "load slot 11, drive 0" command for vol
> vchanger01_0_2.
> 3305 Autochanger "load slot 11, drive 0", status is OK for vol
> vchanger01_0_2.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_2.
> Sending label command for Volume "vchanger01_0_3" Slot 12 ...
> 3307 Issuing autochanger "unload slot 11, drive 0" command for vol
> vchanger01_0_3.
> 3304 Issuing autochanger "load slot 12, drive 0" command for vol
> vchanger01_0_3.
> 3305 Autochanger "load slot 12, drive 0", status is OK for vol
> vchanger01_0_3.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_3.
> Sending label command for Volume "vchanger01_0_4" Slot 13 ...
> 3307 Issuing autochanger "unload slot 12, drive 0" command for vol
> vchanger01_0_4.
> 3304 Issuing autochanger "load slot 13, drive 0" command for vol
> vchanger01_0_4.
> 3305 Autochanger "load slot 13, drive 0", status is OK for vol
> vchanger01_0_4.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_4.
> Sending label command for Volume "vchanger01_0_5" Slot 14 ...
> 3307 Issuing autochanger "unload slot 13, drive 0" command for vol
> vchanger01_0_5.
> 3304 Issuing autochanger "load slot 14, drive 0" command for vol
> vchanger01_0_5.
> 3305 Autochanger "load slot 14, drive 0", status is OK for vol
> vchanger01_0_5.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_5.
> Sending label command for Volume "vchanger01_0_6" Slot 15 ...
> 3307 Issuing autochanger "unload slot 14, drive 0" command for vol
> vchanger01_0_6.
> 3304 Issuing autochanger "load slot 15, drive 0" command for vol
> vchanger01_0_6.
> 3305 Autochanger "load slot 15, drive 0", status is OK for vol
> vchanger01_0_6.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_6.
> Sending label command for Volume "vchanger01_0_7" Slot 16 ...
> 3307 Issuing autochanger "unload slot 15, drive 0" command for vol
> vchanger01_0_7.
> 3304 Issuing autochanger "load slot 16, drive 0" command for vol
> vchanger01_0_7.
> 3305 Autochanger "load slot 16, drive 0", status is OK for vol
> vchanger01_0_7.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_7.
> Sending label command for Volume "vchanger01_0_8" Slot 17 ...
> 3307 Issuing autochanger "unload slot 16, drive 0" command for vol
> vchanger01_0_8.
> 3304 Issuing autochanger "load slot 17, drive 0" command for vol
> vchanger01_0_8.
> 3305 Autochanger "load slot 17, drive 0", status is OK for vol
> vchanger01_0_8.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_8.
> Sending label command for Volume "vchanger01_0_9" Slot 18 ...
> 3307 Issuing autochanger "unload slot 17, drive 0" command for vol
> vchanger01_0_9.
> 3304 Issuing autochanger "load slot 18, drive 0" command for vol
> vchanger01_0_9.
> 3305 Autochanger "load slot 18, drive 0", status is OK for vol
> vchanger01_0_9.
> 3920 Cannot label Volume because it is already labeled: "vchanger01_0_0"
> Label command failed for Volume vchanger01_0_9.
> yes
> yes: is an invalid command.
>
> This entry "3920 Cannot label Volume because it is already labeled:
> "vchanger01_0_0"" keeps appearing in the vchanger log for slots 2 -18.
>
> Appreciate any assistance to resolve the above issue.
>
> Thanks in advance.
>
> Pann
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data
> untouched!https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
>
>
>
> _______________________________________________
> Bacula-users mailing
> listBacula-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
>
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
