On Tue, Jan 5, 2010 at 4:26 AM, Javier Barroso <javibarr...@gmail.com> wrote: > Hi people, > > First, I'm using an old bacula version (etch version 1.38.11-8), so I > now this is a 2006 question :( > > I have a problem, I searched in this list and your bugtracker, but I > couldn't find any response which solve my issue. > > Today, after recover from an autochanger issue (see thread about > scsi), bacula is telling me about mount a volume: > > 05-Jan 09:48 backup-sd: 3301 Issuing autochanger "loaded drive 0" command. > 05-Jan 09:48 backup-sd: 3302 Autochanger "loaded drive 0", result is Slot 4. > 05-Jan 09:48 backup-sd: 3301 Issuing autochanger "loaded drive 0" command. > 05-Jan 09:48 backup-sd: 3302 Autochanger "loaded drive 0", result is Slot 4. > 05-Jan 09:48 backup-sd: 3301 Issuing autochanger "loaded drive 0" command. > 05-Jan 09:48 backup-sd: 3302 Autochanger "loaded drive 0", result is Slot 4. > 05-Jan 09:48 backup-sd: Please mount Volume "ISOLAD01" on Storage > Device "Drive-1" (/dev/st0) for Job openbravodb.2010-01-04_20.00.06 > > However, this volume is mounted: > > # mtx -f /dev/autochanger1 status > Storage Changer /dev/autochanger1:4 Drives, 60 Slots ( 2 Import/Export ) > Data Transfer Element 0:Full (Storage Element 4 Loaded):VolumeTag = > ISOLAD01 > Data Transfer Element 1:Empty > Data Transfer Element 2:Empty > Data Transfer Element 3:Empty > > *mount > The defined Storage resources are: > 1: File > 2: ultrium4-1 > 3: ultrium4-2 > Select Storage resource (1-3): 2 > 3001 OK mount. Device="Drive-1" (/dev/st0) > *status storage > The defined Storage resources are: > 1: File > 2: ultrium4-1 > 3: ultrium4-2 > Select Storage resource (1-3): 2 > Connecting to Storage daemon ultrium4-1 at 192.168.110.26:9103 > > backup-sd Version: 1.38.11 (28 June 2006) i486-pc-linux-gnu debian 4.0 > Daemon started 05-ene-10 09:43, 0 Jobs run since started. > > Running Jobs: > Writing: Full Backup job openbravodb JobId=14858 Volume="ISOLAD01" > pool="DiarioLunes" device=""Drive-1" (/dev/st0)" > Files=0 Bytes=0 Bytes/sec=0 > FDReadSeqNo=6 in_msg=6 out_msg=4 fd=8 > ==== > > Jobs waiting to reserve a drive: > ==== > > Terminated Jobs: > JobId Level Files Bytes Status Finished Name > ====================================================================== > 14842 Full 0 0 Error 01-ene-10 18:04 webserver > 14843 Full 0 0 Other 01-ene-10 18:34 bender > 14844 Full 0 0 Error 01-ene-10 18:39 geocisa > 14845 Full 0 0 Error 01-ene-10 18:44 nagios > 14847 Full 0 0 Error 01-ene-10 18:49 titan > 14848 Full 0 0 Error 01-ene-10 18:54 redmine > 14849 Full 0 0 Error 01-ene-10 18:59 > svn.isotrol.com > 14850 Full 0 0 Error 01-ene-10 19:04 sprdom > 14851 Full 0 0 Error 01-ene-10 19:10 BackupCatalog > 14846 Full 0 0 Other 01-ene-10 19:14 admon > ==== > > Device status: > Autochanger "Autochanger" with devices: > "Drive-1" (/dev/st0) > Device "FileStorage" (/tmp) is not open or does not exist. > Device "Drive-1" (/dev/st0) open but no Bacula volume is mounted. > Device is BLOCKED waiting for media. > Slot 4 is loaded in drive 0. > Total Bytes Read=0 Blocks Read=0 Bytes/block=0 > Positioned at File=0 Block=0 > Device "Drive-2" (/dev/st1) open but no Bacula volume is mounted. > Total Bytes Read=0 Blocks Read=0 Bytes/block=0 > Positioned at File=0 Block=0 > ==== > > In Use Volume status: > ISOLAD01 on device "Drive-1" (/dev/st0) > ==== > You have messages. > * mess > *mess > 05-Jan 10:10 backup-sd: 3301 Issuing autochanger "loaded drive 0" command. > 05-Jan 10:10 backup-sd: 3302 Autochanger "loaded drive 0", result is Slot 4. > 05-Jan 10:10 backup-sd: 3301 Issuing autochanger "loaded drive 0" command. > 05-Jan 10:10 backup-sd: 3302 Autochanger "loaded drive 0", result is Slot 4. > 05-Jan 10:10 backup-sd: Please mount Volume "ISOLAD01" on Storage > Device "Drive-1" (/dev/st0) for Job openbravodb.2010-01-04_20.00.06 > > If I do a "update slots", bacula umount this volume: > *update slots > The defined Storage resources are: > 1: File > 2: ultrium4-1 > 3: ultrium4-2 > Select Storage resource (1-3): 2 > Connecting to Storage daemon ultrium4-1 at 192.168.110.26:9103 ... > 3306 Issuing autochanger "slots" command. > Device "Drive-1" has 60 slots. > Connecting to Storage daemon ultrium4-1 at 192.168.110.26:9103 ... > 3301 Issuing autochanger "loaded drive 0" command. > 3302 Autochanger "loaded drive 0", result is Slot 4. > 3307 Issuing autochanger "unload slot 4, drive 0" command. > 3306 Issuing autochanger "list" command. > Catalog record for Volume "ISOVBF04" updated to reference slot 1. > Catalog record for Volume "ISOXAD02" updated to reference slot 2. > Catalog record for Volume "ISOVAF03" updated to reference slot 3. > Catalog record for Volume "ISOLAD01" updated to reference slot 4. > Catalog record for Volume "ISOMAD01" updated to reference slot 5. > Catalog record for Volume "ISOXAD01" updated to reference slot 6. > Catalog record for Volume "ISOVBF03" updated to reference slot 7. > Volume "ISOLBD01" not found in catalog. Slot=8 InChanger set to zero. > Catalog record for Volume "ISOVAF04" updated to reference slot 9. > Catalog record for Volume "ISOVAF02" updated to reference slot 10. > Catalog record for Volume "ISOJBD01" updated to reference slot 11. > Catalog record for Volume "ISOVAF05" updated to reference slot 12. > Catalog record for Volume "ISOMAD02" updated to reference slot 13. > Catalog record for Volume "ISOJAD02" updated to reference slot 14. > Catalog record for Volume "ISOLAD02" updated to reference slot 15. > Catalog record for Volume "ISOVBF01" updated to reference slot 19. > Catalog record for Volume "ISOVBF02" updated to reference slot 20. > Catalog record for Volume "ISOVBF05" updated to reference slot 30. > Volume "ISOJAD01" not found in catalog. Slot=31 InChanger set to zero. > > # mtx -f /dev/autochanger1 status > Storage Changer /dev/autochanger1:4 Drives, 60 Slots ( 2 Import/Export ) > Data Transfer Element 0:Empty > Data Transfer Element 1:Empty > Data Transfer Element 2:Empty > Data Transfer Element 3:Empty > > *status storage > Device status: > Autochanger "Autochanger" with devices: > "Drive-1" (/dev/st0) > Device "FileStorage" (/tmp) is not open or does not exist. > Device "Drive-1" (/dev/st0) is not open or does not exist. > Device is BLOCKED waiting for media. > Drive 0 is not loaded. > Device "Drive-2" (/dev/st1) open but no Bacula volume is mounted. > Total Bytes Read=0 Blocks Read=0 Bytes/block=0 > Positioned at File=0 Block=0 > ==== > > In Use Volume status: > ==== > > *umount > The defined Storage resources are: > 1: File > 2: ultrium4-1 > 3: ultrium4-2 > Select Storage resource (1-3): 2 > 3901 Device "Drive-1" (/dev/st0) is already unmounted. > > # mtx -f /dev/autochanger1 load 4 0 > * mount > * status storage > ... > Device status: > Autochanger "Autochanger" with devices: > "Drive-1" (/dev/st0) > Device "FileStorage" (/tmp) is not open or does not exist. > Device "Drive-1" (/dev/st0) open but no Bacula volume is mounted. > Device is BLOCKED waiting for media. > Slot 4 is loaded in drive 0. > Total Bytes Read=0 Blocks Read=0 Bytes/block=0 > Positioned at File=0 Block=0 > Device "Drive-2" (/dev/st1) open but no Bacula volume is mounted. > Total Bytes Read=0 Blocks Read=0 Bytes/block=0 > Positioned at File=0 Block=0 > ==== > > In Use Volume status: > ISOLAD01 on device "Drive-1" (/dev/st0) > ==== > You have messages > * > 05-Jan 10:18 backup-sd: 3301 Issuing autochanger "loaded drive 0" command. > 05-Jan 10:18 backup-sd: 3302 Autochanger "loaded drive 0", result is Slot 4. > 05-Jan 10:18 backup-sd: 3301 Issuing autochanger "loaded drive 0" command. > 05-Jan 10:18 backup-sd: 3302 Autochanger "loaded drive 0", result is Slot 4. > 05-Jan 10:18 backup-sd: 3301 Issuing autochanger "loaded drive 0" command. > 05-Jan 10:18 backup-sd: 3302 Autochanger "loaded drive 0", result is Slot 4. > 05-Jan 10:18 backup-sd: Please mount Volume "ISOLAD01" on Storage > Device "Drive-1" (/dev/st0) for Job openbravodb.2010-01-04_20.00.06 > > # ISOLAD01 is a volume in bacula db > * list media pool=DiarioLunes > Pool: DiarioLunes > +---------+------------+-----------+-----------------+----------+--------------+---------+------+-----------+---------------+---------------------+ > | MediaId | VolumeName | VolStatus | VolBytes | VolFiles | > VolRetention | Recycle | Slot | InChanger | MediaType | > LastWritten | > +---------+------------+-----------+-----------------+----------+--------------+---------+------+-----------+---------------+---------------------+ > | 51 | ISOLAD01 | Append | 371,662,282,376 | 523 | > 518,400 | 1 | 4 | 1 | Ultrium3-SCSI | 2009-10-20 > 02:33:52 | > > So, what am I missing ? Any help is appreciated.
Nothing. There are bugs like this in 1.38. 1) Change /dev/st0 to /dev/nst0 in your config so bacula does not accidentally delete one of your volumes. 2) Stop bacula-sd 3) Manually remove the tape using the autohanger command 4) Restart bacula-sd. Your jobs probably will have been terminated by this action. > > I would like to ask another question ... How difficult is upgrading > from 1.38 to 2.4 and then to 3.0? Are there many differences between > config files between these bacula versions, or are backward compatible > ? > > Thank you very much. > I would go to 2.4 first. There is not that much configuration change but your database will need to be upgraded. On debian I believe the installer will auto upgrade the database. John ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
