Hello, Is anyone able to suggest anything, or point me in a direction? Have I hit an unknown bug as I can't think what else to try.
My bacula-sd.conf looks like this. Please see additional information below. ---------- Storage { # definition of myself Name = iota-sd SDPort = 9103 # Director's port WorkingDirectory = "/var/spool/bacula" Pid Directory = "/var/run" Maximum Concurrent Jobs = 20 } Director { Name = iota-dir Password = "###" } # NEO2000 tapedrive1 Device { Name = NeoLTO3-0 Drive Index = 0 Media Type = LTO3 Archive Device = /dev/nst0 Device Type = Tape AutoChanger = yes; AutomaticMount = yes; AutoSelect = yes; AlwaysOpen = no; RemovableMedia = yes; RandomAccess = no; Maximum Network Buffer Size = 262144 Maximum File Size = 10gb Minimum blocksize = 262144 Maximum blocksize = 262144 Spool Directory = /bacula-spool/1/ } # NEO2000 jukebox Autochanger { Name = NEO2000-1 Device = NeoLTO3-0 Changer Command = "/usr/libexec/bacula/mtx-changer %c %o %S %a %d" Changer Device = /dev/sg13 } Messages { Name = Standard director = iota-dir = all } -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. -----Original Message----- From: GILES Stephen Sent: 15 February 2013 10:32 To: bacula-users@lists.sourceforge.net Subject: [Bacula-users] difficulty reading tapes after upgrade 3.0.2 -> 5.2.12 Hello, I've recently upgraded my bacula server. It was running 3.0.2 on centos 5 to 5.2.12 on centos 6 The 2 database steps upgraded fine, and the server works as expected with my file based storage demons. However, I cannot seem to get my previously written tapes to read using the new bacula. The tapes load (30 slot LTO3 jukebox) but when they try to mount I get the error : Volume data error at 0:0! Wanted ID: "BB02", got "UUUU". Buffer discarded I use and have used fixed 256K block lengths, so I checked my configuration. This is still in place. I used this for speed issues when writing to tape in previous versions. I can read the tapes by hand (the 1st block is 1K and the rest are 256K blocks) which were tapes written by bacula and have been running for many years without issues. The tape read testing have been done using the command : dd if=/dev/nst0 of=/tmp/test_Block1k ibs=1k count=1 And dd if=/dev/nst0 of=/tmp/test_Block1k ibs=256k count=1 No matter what I do with the block size, I can't get bacula to read and old tape, even though they read fine with dd (I can see the BB02 header etc). And the old version of bacula, with an almost identical config, and the same hardware. If I remove the old tape from the catalogue and re-label it with new bacula, the new tape reads mounts and write fine. However ALL of the blocks on the tape are 256K from the very start. Has there been a change in tape formatting between 3.0 and 5.2? I have read the release notes but can't see anything about that. A failed bacula SD debug log (1000) looks like this ----- iota-sd: autochanger.c:195-0 load slot 2, drive 0, status is OK. iota-sd: autochanger.c:212-0 load slot 2 status=0 iota-sd: autochanger.c:327-0 Unlocking changer NEO2000-1 iota-sd: autochanger.c:218-0 After changer, status=0 iota-sd: dev.c:383-0 open dev: type=2 dev_name="NeoLTO3-0" (/dev/nst0) vol= mode=OPEN_READ_ONLY iota-sd: dev.c:1911-0 Enter mount iota-sd: dev.c:433-0 Open dev: device is tape iota-sd: dev.c:448-0 Try open "NeoLTO3-0" (/dev/nst0) mode=OPEN_READ_ONLY iota-sd: dev.c:470-0 Rewind after open iota-sd: dev.c:2411-0 In set_os_device_parameters iota-sd: dev.c:2433-0 MTSETDRVBUFFER iota-sd: dev.c:522-0 open dev: tape 5 opened iota-sd: dev.c:396-0 preserve=0x0 fd=5 iota-sd: lock.c:285-0 steal lock. old=BST_NOT_BLOCKED from dircmd.c:572 iota-sd: lock.c:290-0 steal lock. new=BST_DOING_ACQUIRE iota-sd: label.c:79-0 Enter read_volume_label res=0 device="NeoLTO3-0" (/dev/nst0) vol= dev_Vol=*NULL* iota-sd: dev.c:598-0 rewind res=0 fd=5 "NeoLTO3-0" (/dev/nst0) iota-sd: label.c:128-0 Big if statement in read_volume_label iota-sd: block.c:992-0 Full read in read_block_from_device() len=262144 iota-sd: block.c:1053-0 Read device got 1024 bytes at 0:0 iota-sd: block.c:292-0 block.c:291 Volume data error at 0:0! Wanted ID: "BB02", got "UUUU". Buffer discarded. iota-sd: message.c:1257-0 Enter Jmsg type=4 iota-sd: label.c:133-0 Requested Volume "" on "NeoLTO3-0" (/dev/nst0) is not a Bacula labeled Volume, because: ERR=block.c:291 Volume data error at 0:0! Wanted ID: "BB02", got "UUUU". Buffer discarded. iota-sd: record.c:269-0 Enter free_record. iota-sd: record.c:273-0 Data buf is freed. iota-sd: record.c:275-0 Leave free_record. iota-sd: label.c:161-0 No volume label - bailing out iota-sd: dev.c:598-0 rewind res=0 fd=5 "NeoLTO3-0" (/dev/nst0) iota-sd: label.c:249-0 return 3 iota-sd: vol_mgr.c:544-0 vol_unused: no vol on "NeoLTO3-0" (/dev/nst0) iota-sd: lock.c:302-0 return lock. old=BST_DOING_ACQUIRE from dircmd.c:588 iota-sd: lock.c:307-0 return lock. new=BST_NOT_BLOCKED iota-sd: dev.c:1746-0 close_dev "NeoLTO3-0" (/dev/nst0) iota-sd: dev.c:598-0 rewind res=0 fd=5 "NeoLTO3-0" (/dev/nst0) iota-sd: dev.c:1944-0 Enter unmount iota-sd: dev.c:1735-0 Clear volhdr vol= iota-sd: acquire.c:731-0 Enter detach_dcr_from_dev iota-sd: block.c:182-0 free_block buffer b4841460 iota-sd: block.c:184-0 free_block block b4801508 iota-sd: record.c:269-0 Enter free_record. iota-sd: record.c:273-0 Data buf is freed. iota-sd: record.c:275-0 Leave free_record. iota-sd: pythonlib.c:225-0 No startup module. iota-sd: sd_plugins.c:111-0 No bplugin_list: generate_plugin_event ignored. iota-sd: job.c:355-0 End Job JobId=0 b4800480 iota-sd: job.c:357-0 Send terminate jid=0 b4800480 iota-sd: message.c:504-0 Close_msg jcr=b4800480 iota-sd: message.c:504-0 Close_msg jcr=0 iota-sd: message.c:524-0 ===Begin close msg resource at 970a930 iota-sd: message.c:609-0 Done walking message chain. iota-sd: message.c:616-0 ===End close msg resource ----- If you want all my configs I am happy to provide them. My bacula-dir is big so don't want to spam the list. I've checked my tape drive options and they seem fine. Also, the tape drive and settings are fine, as I can read and write new tapes that are recently labelled. Just not old ones + old tapes with the old setup. Is there something obvious that I'm missing? I've never seen this before and there is very little on the mailing lists relating to the BB02 header and UUUU response error message. Anyone have any ideas or pointers? Thanks, Stephen. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users