[Bacula-users] Fiber channel tapes permanent name howto ?

2010-10-27 Thread Javier Barroso
Hi,

I'm having the same problem that other thread in november 2008:
http://sourceforge.net/mailarchive/message.php?msg_id=BBDDF0B7CFFFCE4FB5110F0A37CE60030942EE%40q.leblancnet.us

But I can't find a solution ...

I have a autochanger rule in udev that points /dev/autochanger1 to /dev/sgX

My problem is that this autochanger has 4 drives, and I cannot get
serial number or other attributes which change, and when I reboot I
will have to change bacula config every time.

My lsscsi output (There is a autochanger and a NSR, 2 fc drives and 2
scsi drives):

# lsscsi
[0:0:0:0]mediumx HP   MSL6000 Series   0520  /dev/sch0
[0:0:0:1]tapeHP   Ultrium 3-SCSI   G63W  /dev/st2
[0:0:0:2]tapeHP   Ultrium 3-SCSI   G63W  /dev/st3
[0:0:0:3]storage HP   NS E1200-320 593d  -
[0:0:1:0]storage HP   HSV200   5110  -
[0:0:2:0]storage HP   HSV200   5110  -
[1:0:0:0]cd/dvd  TEAC CD-224E  9.9A  /dev/sr0
[3:0:3:0]tapeHP   Ultrium 3-SCSI   G63W  /dev/st0
[3:0:4:0]tapeHP   Ultrium 3-SCSI   G54W  /dev/st1

I can't use /dev/tape/by-path, because these devices could change,
this is the ls output:

# ls /dev/tape/by-path/ -l
total 0
lrwxrwxrwx 1 root root  9 oct 26 16:18
pci-:03:01.0-fc-0x10e002239fa8:0x0001 - ../../st2
lrwxrwxrwx 1 root root 10 oct 26 16:18
pci-:03:01.0-fc-0x10e002239fa8:0x0001-nst -
../../nst2
lrwxrwxrwx 1 root root  9 oct 26 16:18
pci-:03:01.0-fc-0x10e002239fa8:0x0002 - ../../st3
lrwxrwxrwx 1 root root 10 oct 26 16:18
pci-:03:01.0-fc-0x10e002239fa8:0x0002-nst -
../../nst3
lrwxrwxrwx 1 root root  9 oct 26 16:17 pci-:06:01.0-scsi-0:0:3:0
- ../../st0
lrwxrwxrwx 1 root root 10 oct 26 16:17
pci-:06:01.0-scsi-0:0:3:0-nst - ../../nst0
lrwxrwxrwx 1 root root  9 oct 26 16:18 pci-:06:01.0-scsi-0:0:4:0
- ../../st1
lrwxrwxrwx 1 root root 10 oct 26 16:18
pci-:06:01.0-scsi-0:0:4:0-nst - ../../nst1

03:01 will change (I guess) like 06.01 ..

I don't know how can I generate /dev/tape/by-id, currently (debian
squeeze) only see one device which is the autochanger:
# ls -l /dev/tape/by-id/
total 0
lrwxrwxrwx 1 root root 9 oct 26 16:18 scsi-200900de6064f - ../../sg3

When I try to guess any difference from st2 and st3 , I don't find
which attribute could I use to generate udev rules:

Here is the diff output from udevadm info --attribute-walk
--path=/sys/class/scsi_tape/st?)

# diff (udevadm info --attribute-walk
--path=/sys/class/scsi_tape/st2) (udevadm info --attribute-walk
--path=/sys/class/scsi_tape/st3)
8,9c8,9
   looking at device
'/devices/pci:03/:03:01.0/host0/rport-0:0-2/target0:0:0/0:0:0:1/scsi_tape/st2':
 KERNEL==st2
---
   looking at device 
 '/devices/pci:03/:03:01.0/host0/rport-0:0-2/target0:0:0/0:0:0:2/scsi_tape/st3':
 KERNEL==st3
18,19c18,19
   looking at parent device
'/devices/pci:03/:03:01.0/host0/rport-0:0-2/target0:0:0/0:0:0:1':
 KERNELS==0:0:0:1
---
   looking at parent device 
 '/devices/pci:03/:03:01.0/host0/rport-0:0-2/target0:0:0/0:0:0:2':
 KERNELS==0:0:0:2
31,33c31,33
 ATTRS{iorequest_cnt}==0xd6beb
 ATTRS{iodone_cnt}==0xd6beb
 ATTRS{ioerr_cnt}==0x3b
---
 ATTRS{iorequest_cnt}==0x1e
 ATTRS{iodone_cnt}==0x1e
 ATTRS{ioerr_cnt}==0x13

I guess I can't use KERNEL nor KERNELS variables and neither counters.

So, are there something that I can do to get my devices with a
permanents names ?

Thank you very much!

--
Nokia and ATT present the 2010 Calling All Innovators-North America contest
Create new apps  games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] No bacula volume is mounted, but the volume is in use on the same device

2010-01-06 Thread Javier Barroso
Hi,
On Tue, Jan 5, 2010 at 12:36 PM, Javier Barroso javibarr...@gmail.com wrote:
 On Tue, Jan 5, 2010 at 12:18 PM, John Drescher dresche...@gmail.com wrote:
 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 :(
 ...
 # 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.

 Thank you very much, I'll try it the next time it happens (I'll change
 my config like in your tip)
Ok, so I tried it again, and the same issue (bacula want a tape which
is mounted, but it doesn't recognize)

I tracked the problem i turned on debug in mtx-changer, and see about
mt -f /dev/nst0 status was telling mt: /dev/nst0: No medium found

Then I tried mt -f with the others three devices (I have an
autochanger with /dev/nst{0,1,2,3} as tapes) and see only nst2 was
online.

I changed my config to /dev/nst2, and bacula is now working again.

But I'm confused now ! :( :(. Somebody can explain me this situation ?:

# mtx -f /dev/autochanger1 status | head -6
  Storage Changer /dev/autochanger1:4 Drives, 60 Slots ( 2 Import/Export )
Data Transfer Element 0:Full (Storage Element 2 Loaded):VolumeTag =
ISOXAD02
Data Transfer Element 1:Empty
Data Transfer Element 2:Empty
Data Transfer Element 3:Empty

# lsscsi
[0:0:0:0]mediumx HP   MSL6000 Series   0520  /dev/sch0
[0:0:0:1]tapeHP   Ultrium 3-SCSI   G63W  /dev/st2
[0:0:0:2]tapeHP   Ultrium 3-SCSI   G63W  /dev/st3
[0:0:0:3]storage HP   NS E1200-320 593d  -
[1:0:3:0]tapeHP   Ultrium 3-SCSI   G63W  /dev/st0
[1:0:4:0]tapeHP   Ultrium 3-SCSI   G54W  /dev/st1

I can guess that first Data Transfer element listed in mtx -f dev
status is the first tape found in lsscsi command output. Then Data
Transfert Element 1 will be /dev/st3 and go ...

Is this true ? Should i name my devices with some persistente name
like /dev/tape1 ?

And more important, why are others (three) devices like not medium found ?

See next session (first I loaded 4 tapes):
# mtx -f /dev/autochanger1 status | head -10
  Storage Changer /dev/autochanger1:4 Drives, 60 Slots ( 2 Import/Export )
Data Transfer Element 0:Full (Storage Element 2 Loaded):VolumeTag =
ISOXAD02
Data Transfer Element 1:Full (Storage Element 1 Loaded):VolumeTag =
ISOVBF04
Data Transfer Element 2:Full (Storage Element 3 Loaded):VolumeTag =
ISOVAF03
Data Transfer Element 3:Full (Storage Element 4 Loaded):VolumeTag =
ISOLAD01

# Bacula is using Data  Transfer Element 0:
* st st
...
Device Drive-1 (/dev/nst2) is mounted with Volume=ISOXAD02
Pool=DiarioMiercoles
...

# But nst3 device is not ready, a while ago nst0 and nst1 wasn't ONLINE yet:
# mt -f /dev

Re: [Bacula-users] No bacula volume is mounted, but the volume is in use on the same device

2010-01-06 Thread Javier Barroso
Hi again,

On Thu, Jan 7, 2010 at 12:27 AM, Javier Barroso javibarr...@gmail.com wrote:
 Hi,
 On Tue, Jan 5, 2010 at 12:36 PM, Javier Barroso javibarr...@gmail.com wrote:
 On Tue, Jan 5, 2010 at 12:18 PM, John Drescher dresche...@gmail.com wrote:
 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 :(
 ...
 # 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.

 Thank you very much, I'll try it the next time it happens (I'll change
 my config like in your tip)
 Ok, so I tried it again, and the same issue (bacula want a tape which
 is mounted, but it doesn't recognize)

 I tracked the problem i turned on debug in mtx-changer, and see about
 mt -f /dev/nst0 status was telling mt: /dev/nst0: No medium found

 Then I tried mt -f with the others three devices (I have an
 autochanger with /dev/nst{0,1,2,3} as tapes) and see only nst2 was
 online.

 I changed my config to /dev/nst2, and bacula is now working again.

 But I'm confused now ! :( :(. Somebody can explain me this situation ?:

 # mtx -f /dev/autochanger1 status | head -6
  Storage Changer /dev/autochanger1:4 Drives, 60 Slots ( 2 Import/Export )
 Data Transfer Element 0:Full (Storage Element 2 Loaded):VolumeTag =
 ISOXAD02
 Data Transfer Element 1:Empty
 Data Transfer Element 2:Empty
 Data Transfer Element 3:Empty

 # lsscsi
 [0:0:0:0]    mediumx HP       MSL6000 Series   0520  /dev/sch0
 [0:0:0:1]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st2
 [0:0:0:2]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st3
 [0:0:0:3]    storage HP       NS E1200-320     593d  -
 [1:0:3:0]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st0
 [1:0:4:0]    tape    HP       Ultrium 3-SCSI   G54W  /dev/st1

 I can guess that first Data Transfer element listed in mtx -f dev
 status is the first tape found in lsscsi command output. Then Data
 Transfert Element 1 will be /dev/st3 and go ...

 Is this true ? Should i name my devices with some persistente name
 like /dev/tape1 ?

 And more important, why are others (three) devices like not medium found ?

 See next session (first I loaded 4 tapes):
 # mtx -f /dev/autochanger1 status | head -10
  Storage Changer /dev/autochanger1:4 Drives, 60 Slots ( 2 Import/Export )
 Data Transfer Element 0:Full (Storage Element 2 Loaded):VolumeTag =
 ISOXAD02
 Data Transfer Element 1:Full (Storage Element 1 Loaded):VolumeTag =
 ISOVBF04
 Data Transfer Element 2:Full (Storage Element 3 Loaded):VolumeTag =
 ISOVAF03
 Data Transfer Element 3:Full (Storage Element 4 Loaded):VolumeTag =
 ISOLAD01

 # Bacula is using Data  Transfer Element 0:
 * st st
 ...
 Device Drive-1 (/dev/nst2

Re: [Bacula-users] Is there any scsi list ? (MSL6000 problem)

2010-01-05 Thread Javier Barroso
On Fri, Nov 6, 2009 at 6:23 PM, Alan Brown a...@mssl.ucl.ac.uk wrote:
 On Fri, 6 Nov 2009, Javier Barroso wrote:

 I'm tracking the problem with HP:
 http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1384395

 I think could be this issue:
 http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=encc=usobjectID=c01744425jumpid=reg_R1002_USEN

 My experience has always been to apply the latest firmware and then talk
 to HP...
Finally, HP replaced my NSR and I had to reconfigure it.

Now bacula is viewing my autochanger, but it didn't working yet. I'll
post a new thread to ask about this issue :(

Thank you very much

--
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


[Bacula-users] No bacula volume is mounted, but the volume is in use on the same device

2010-01-05 Thread Javier Barroso
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   FinishedName
==
 14842  Full  0  0 Error01-ene-10 18:04 webserver
 14843  Full  0  0 Other01-ene-10 18:34 bender
 14844  Full  0  0 Error01-ene-10 18:39 geocisa
 14845  Full  0  0 Error01-ene-10 18:44 nagios
 14847  Full  0  0 Error01-ene-10 18:49 titan
 14848  Full  0  0 Error01-ene-10 18:54 redmine
 14849  Full  0  0 Error01-ene-10 18:59 svn.isotrol.com
 14850  Full  0  0 Error01-ene-10 19:04 sprdom
 14851  Full  0  0 Error01-ene-10 19:10 BackupCatalog
 14846  Full  0  0 Other01-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.

Re: [Bacula-users] No bacula volume is mounted, but the volume is in use on the same device

2010-01-05 Thread Javier Barroso
On Tue, Jan 5, 2010 at 12:18 PM, John Drescher dresche...@gmail.com wrote:
 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 :(
...
 # 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.

Thank you very much, I'll try it the next time it happens (I'll change
my config like in your tip)

 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.

Another (I hope last) Are bacula 1.38 cilents are compatible with
bacula 2.4 server?, or I need upgrade all my clients in the same time
than the server ? I search in 2.4 manual [1] and in wiki, but didn't
find anything

Thanks

http://www.bacula.org/en/rel-manual/index.html

--
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


Re: [Bacula-users] Is there any scsi list ? (MSL6000 problem)

2009-11-03 Thread Javier Barroso
Hi again,

On Tue, Nov 3, 2009 at 11:54 AM, Javi Barroso javibarr...@gmail.com wrote:
 Hi,

 I'm having trouble with a MSL6000 tape cabine.

 I would like to ask to help, but I don't known which is the appropiate
 list.

 So, I'm asking you about the problem, and I'll be appreciate any
 pointer.

 My problem:

 I have a -old (debian sarge)- bacula system with a MSL6000 attached
 with fiber channel. This system was working until 2 weeks ago.

 The logs are (a lot of times):
 Bacula:
 28-Oct 01:47 backup-sd: BackupCatalog.2009-10-27_20.00.22 Fatal error:
 3992 Bad autochanger load slot 5, drive 0: ERR=Child died from
 signal 15: Termination.
 28-Oct 01:47 backup-fd: BackupCatalog.2009-10-27_20.00.22 Fatal error:
 job.c:1617 Bad response to Append Data command. Wanted 3000 OK data
 , got 3903 Error append data

 /var/log/messages:
 Oct 23 15:31:04 backup kernel: st0: Error 7 (sugg. bt 0x0, driver
 bt 0x0, host bt 0x7).

 Command line:
 # mtx -f /dev/autochanger1 status
 cannot open SCSI device '/dev/autochanger1' - No such file or
 directory
 # ls -l /dev/autochanger1
 lrwxrwxrwx 1 root root 3 2009-10-30 09:47 /dev/autochanger1 - sg4

 The device MSL6000 seems to be present in the system:
 # lsscsi -g
 [0:0:0:0]    storage HP       HSV200           5110  -         /dev/
 sg0
 [0:0:1:0]    storage HP       HSV200           5110  -         /dev/
 sg1
 [0:0:2:0]    mediumx HP       MSL6000 Series   0520  /dev/sch0  /dev/
 sg4
 [0:0:2:1]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st2  /dev/
 sg5
 [0:0:2:2]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st3  /dev/
 sg6
 [0:0:2:3]    storage HP       NS E1200-320     571f  -         /dev/
 sg7
 [1:0:3:0]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st0  /dev/
 sg2
 [1:0:4:0]    tape    HP       Ultrium 3-SCSI   G54W  /dev/st1  /dev/
 sg3

 When I try to remove and add, it dissappear:
 # echo scsi remove-single-device 0 0 2 0  /proc/scsi/scsi
 # echo scsi add-single-device 0 0 2 0  /proc/scsi/scsi
 # dmesg
 lpfc :03:01.0: 0:0713 SCSI layer issued LUN reset (2, 0) Data:
 x2002 x3 x2
 lpfc :03:01.0: 0:0714 SCSI layer issued Bus Reset Data: x2002
 scsi 0:0:2:0: scsi: Device offlined - not ready after error recovery

 # lsscsi -g
 [0:0:0:0]    storage HP       HSV200           5110  -         /dev/
 sg0
 [0:0:1:0]    storage HP       HSV200           5110  -         /dev/
 sg1
 [0:0:2:1]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st2  /dev/
 sg5
 [0:0:2:2]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st3  /dev/
 sg6
 [0:0:2:3]    storage HP       NS E1200-320     571f  -         /dev/
 sg7
 [1:0:3:0]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st0  /dev/
 sg2
 [1:0:4:0]    tape    HP       Ultrium 3-SCSI   G54W  /dev/st1  /dev/
 sg3

 If then I reboot the system, 2 tapes , NS E1200-320 and MSL6000
 dissappear (all connected by fiber channel):
 # lsscsi
 [0:0:0:0]    storage HP       HSV200           5110  -
 [0:0:1:0]    storage HP       HSV200           5110  -
 [1:0:3:0]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st0
 [1:0:4:0]    tape    HP       Ultrium 3-SCSI   G54W  /dev/st1

 Two tapes are connected by scsi wire.

 If I power off - power on MSL6000 linux get the device:

 # dmesg
  Vendor: HP        Model: MSL6000 Series    Rev: 0520
  Type:   Medium Changer                     ANSI SCSI revision: 02
  Vendor: HP        Model: Ultrium 3-SCSI    Rev: G63W
  Type:   Sequential-Access                  ANSI SCSI revision: 03
 st 0:0:2:1: Attached scsi tape st2
 st2: try direct i/o: yes (alignment 512 B)
  Vendor: HP        Model: Ultrium 3-SCSI    Rev: G63W
  Type:   Sequential-Access                  ANSI SCSI revision: 03
 st 0:0:2:2: Attached scsi tape st3
 st3: try direct i/o: yes (alignment 512 B)
  Vendor: HP        Model: NS E1200-320      Rev: 571f
  Type:   RAID                               ANSI SCSI revision: 04
 SCSI Media Changer driver v0.25
 ch0: type #1 (mt): 0x0+1 [medium transport]
 ch0: type #2 (st): 0x20+58 [storage]
 ch0: type #3 (ie): 0x1c0+2 [import/export]
 ch0: type #4 (dt): 0x1e0+4 [data transfer]
 ch0: dt 0x1e0: READ ELEMENT STATUS failed
 ch0: dt 0x1e1: READ ELEMENT STATUS failed
 ch0: dt 0x1e2: READ ELEMENT STATUS failed
 ch0: dt 0x1e3: READ ELEMENT STATUS failed
 ch0: INITIALIZE ELEMENT STATUS, may take some time ...
 ch0: ... finished
 ch 0:0:2:0: Attached scsi changer ch0
 st 1:0:3:0: Attached scsi generic sg0 type 1
 st 1:0:4:0: Attached scsi generic sg1 type 1
 scsi 0:0:0:0: Attached scsi generic sg2 type 12
 scsi 0:0:1:0: Attached scsi generic sg3 type 12
 ch 0:0:2:0: Attached scsi generic sg4 type 8
 st 0:0:2:1: Attached scsi generic sg5 type 1
 st 0:0:2:2: Attached scsi generic sg6 type 1

 Then I can remove and add the device and MSL6000 rescan the labels

 # echo scsi remove-single-device 0 0 2 0  /proc/scsi/scsi
 # echo scsi add-single-device 0 0 2 0  /proc/scsi/scsi
 scsi 0:0:2:3: Attached scsi generic sg7 type 12
  Vendor: HP        Model: MSL6000 Series    Rev: 0520
  Type:   Medium