Backup Central

Hi,

First of all, I'd like to apologise for the cross post, but this has
been knacking me off for 2 weeks now, and I really want to get this
sorted... :)

Having some minor issues with Amanda on OpenBSD3.4, talking to a Dell
Powervault 120T 7-slot changer/drive. After eventually working my way
through the changer scripts I've found that chg-chio is the one for me.
chg-scsi, couldn't figure out the configuration files and couldn't take
to the jukebox, but chg-chio, using the chio program works fine.

The issue that I have now is that I'm finding amtape unreliable at
moving tapes around effectively, and also that it's having problems
rewinding tapes. I don't know if this is an OpenBSD related issue or an
Amanda issue. I'm using the latest release version that I could find on
the site (amanda-2.4.4p3) compiled from source.

Using chio to move tapes between slots works perfectly, so I don't think
it's a changer issue, and I can't find any mention of the error messages
in the changer code. It looks like it's having some issues with regards
to rewinding the tapes, and not handling the time that the tape would
take to rewind. In my configuration, it seems that the taper has no
method of handling the fact that the drive is not ready, and just
returns a file handle open error on /dev/nrst0. I suppose that I would
either need to know how to get the Dell Powervault 120T working under
the chg-scsi driver, or some means of adding a delay into the process to
allow the drive to ready itself before letting ammt get anywhere near
/dev/nrst0.

My configuration is called ltsn. Here is an example of what happens
when changing a tape around:

bash-2.05b# /usr/local/sbin/amtape ltsn slot first
amtape: could not rewind /dev/nrst0: tape_rewind: tape open: /dev/nrst0:
Input/output erroramtape: changed to slot 1 on /dev/nrst0

bash-2.05b# cat /tmp/amanda/amtape.20040714123758.debug
amtape: debug 1 pid 30456 ruid 0 euid 0: start at Wed Jul 14 12:37:58 2004
changer: got exit: 0 str: 2 /dev/nrst0
amtape: pid 30456 finish time Wed Jul 14 12:39:05 2004

bash-2.05b# cat /tmp/amanada/changer.debug
Wed Jul 14 12:43:30 2004: enter: getTapeParams
Wed Jul 14 12:43:30 2004: running: /bin/chio -f /dev/ch0 params
Wed Jul 14 12:43:30 2004: /dev/ch0: 7 slots, 1 drive, 1 picker
Wed Jul 14 12:43:30 2004: /dev/ch0: current picker: 0
Wed Jul 14 12:43:30 2004: leave: getTapeParams: 7, 1, 1
Wed Jul 14 12:43:30 2004: enter: getTapeStatus
Wed Jul 14 12:43:30 2004: running: /bin/chio -f /dev/ch0 status
Wed Jul 14 12:43:31 2004: picker 0:
Wed Jul 14 12:43:31 2004: slot 0: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: slot 1: <ACCESS>
Wed Jul 14 12:43:31 2004: slot 2: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: slot 3: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: slot 4: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: slot 5: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: slot 6: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: drive 0: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: enter: getCurrentTape
Wed Jul 14 12:43:31 2004: leave: getCurrentTape: 2
Wed Jul 14 12:43:31 2004: leave: getTapeStatus: 7
Wed Jul 14 12:43:31 2004MT -> /usr/local/sbin/ammt -f /dev/nrst0 rewind
Wed Jul 14 12:43:31 2004: enter: changeTape: 1
Wed Jul 14 12:43:31 2004: enter: Unload: 2
Wed Jul 14 12:44:13 2004: leave: Unload
Wed Jul 14 12:44:13 2004: enter: Load: 1
Wed Jul 14 12:44:13 2004: running: /bin/chio -f /dev/ch0 move slot 0 drive 0
Wed Jul 14 12:44:37 2004: leave: Load
Wed Jul 14 12:44:37 2004: leave: changeTape
Wed Jul 14 12:44:37 2004: 1 /dev/nrst0

bash-2.05b# chio status
picker 0:
slot 0: <ACCESS>
slot 1: <ACCESS,FULL>
slot 2: <ACCESS,FULL>
slot 3: <ACCESS,FULL>
slot 4: <ACCESS,FULL>
slot 5: <ACCESS,FULL>
slot 6: <ACCESS,FULL>
drive 0: <ACCESS,FULL>

Whilst the drive is not ready, this message appears in the dmesg:

st0(ahc1:3:0): Check Condition on opcode 0x0
SENSE KEY: Not Ready
ASC/ASCQ: Logical Unit Is in Process Of Becoming Ready

And ammt returns this:

bash-2.05b# /usr/local/sbin/ammt -d -f /dev/nrst0 status
debug mode!
syntax: eof -> e
syntax: weof -> w
syntax: fsf -> f
syntax: asf -> a
syntax: bsf -> b
syntax: rewind -> rewi
syntax: offline -> o
syntax: rewoffl -> rewo
syntax: status -> s
tapename is "/dev/nrst0"
calling tape_open("/dev/nrst0",0)
/dev/nrst0 status failed: Input/output error

Eventually, the tape comes online and can be used, after about 30 seconds:

bash-2.05b# /usr/local/sbin/ammt -d -f /dev/nrst0 status
debug mode!
syntax: eof -> e
syntax: weof -> w
syntax: fsf -> f
syntax: asf -> a
syntax: bsf -> b
syntax: rewind -> rewi
syntax: offline -> o
syntax: rewoffl -> rewo
syntax: status -> s
tapename is "/dev/nrst0"
calling tape_open("/dev/nrst0",0)
processing status(1)
calling tapefd_status()
/dev/nrst0 status: ONLINE ds == 0x0003 er == 0x0000

Gaby

--
Ha! Ha! Ha! Loins...
- Phil Ken Sebben

gaby < at > vanhegan.net
http://weblog.vanhegan.net

C R Ritson wrote:

Having some minor issues with Amanda on OpenBSD3.4, talking to
a Dell Powervault 120T 7-slot changer/drive. After eventually
working my way through the changer scripts I've found that
chg-chio is the one for me.
chg-scsi, couldn't figure out the configuration files and
couldn't take to the jukebox, but chg-chio, using the chio
program works fine.


I am using linux and amanda to drive the same Dell changer - but I use
chg-zd-mtx for this. This changer user the mtx command to do the actual
work. mtx is included in our redhat installation, but the chg-zd-mtx
script also gives a sourceforge URL should you wish to try it on
OpenBSD.

All this is guesswork, but may help you.


Thanks, I will give this a try. Is there much configuration required
for chg-zd-mtx?

Gaby

--
Ha! Ha! Ha! Loins...
- Phil Ken Sebben

gaby < at > vanhegan.net
http://weblog.vanhegan.net

On Wed, 14 Jul 2004 at 2:08pm, Gaby Vanhegan wrote

Thanks, I will give this a try. Is there much configuration required
for chg-zd-mtx?

Not really. Look through the chg-zd-mtx script itself (which amanda puts
in /usr/local/libexec by default -- it steps you through the config
process.

--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

I've used that script on three different amanda configs at my
site (only one has some issues and its the oldest of the three
installation, the other two work perfectly).

I did change the shell though, ksh I think helped with some of
the issues on the older installation. YMMV.

On Wed, Jul 14, 2004 at 09:25:58AM -0400, Joshua Baker-LePain wrote:
On Wed, 14 Jul 2004 at 2:08pm, Gaby Vanhegan wrote

Thanks, I will give this a try. Is there much configuration required
for chg-zd-mtx?

Not really. Look through the chg-zd-mtx script itself (which amanda puts
in /usr/local/libexec by default -- it steps you through the config
process.

--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
---
Brian R Cuttler brian.cuttler < at > wadsworth.org
Computer Systems Support (v) 518 486-1697
Wadsworth Center (f) 518 473-6384
NYS Department of Health Help Desk 518 473-0773

On 14 Jul 2004, at 14:25, Joshua Baker-LePain wrote:

On Wed, 14 Jul 2004 at 2:08pm, Gaby Vanhegan wrote

Thanks, I will give this a try. Is there much configuration required
for chg-zd-mtx?

Not really. Look through the chg-zd-mtx script itself (which amanda
puts
in /usr/local/libexec by default -- it steps you through the config
process.

Well, if I could make mtx compile under OpenBSD, that would be lovely.
So far the latest release doesn't. I get:

bash-2.05b# gmake clean
rm -f *.o *~
rm -f mtx tapeinfo loaderinfo scsitape
rm -f mam2debug mam2debug2
bash-2.05b# gmake
gcc -g -O2 -DVERSION="\"1.2.17rel\"" -c -o mtx.o mtx.c
In file included from mtx.c:40:
mtxl.h:35: syntax error before `SCSI_OpenDevice'
mtxl.h:35: warning: data definition has no type or storage class
mtxl.h:36: syntax error before `DEVICE_TYPE'
mtxl.h:37: syntax error before `DeviceFD'
mtxl.h:52: syntax error before `MediumChangerFD'
mtxl.h:54: syntax error before `fd'
mtxl.h:56: syntax error before `MediumChangerFD'
mtxl.h:61: syntax error before `MediumChangerFD'
mtxl.h:62: syntax error before `fd'
mtxl.h:63: syntax error before `fd'
mtx.c:90: syntax error before `MediumChangerFD'
mtx.c:90: `DEVICE_TYPE' undeclared here (not in a function)
mtx.c:90: syntax error before `0'
mtx.c:90: warning: data definition has no type or storage class
gmake: *** [mtx.o] Error 1
bash-2.05b#

Any C people who could assist?

Gaby

--
Uganda Maximum - Enemy of the English Thrust
gaby < at > vanhegan.net
http://weblog.vanhegan.net

On 14 Jul 2004, at 15:14, Gaby vanhegan wrote:

Well, if I could make mtx compile under OpenBSD, that would be lovely.

And I don't think it's going to. Having a look at the errors and the
header files, it's clear that there is simply no device support for
OpenBSD in mtx:

...
/* Now greately modified to use GNU Autoconf stuff: */
/* If we use the 'sg' interface, like Linux, do this: */
#if HAVE_SCSI_SG_H
# include <scsi/scsi.h>
# include <scsi/scsi_ioctl.h>
# include <scsi/sg.h>
typedef int DEVICE_TYPE; /* the sg interface uses this. */
# define HAVE_GET_ID_LUN 1 /* signal that we have it... */
#endif

/* The 'cam' interface, like FreeBSD: */
#if HAVE_CAMLIB_H
# include <camlib.h> /* easy (?) access to the CAM user library. */
# include <cam/cam_ccb.h>
# include <cam/scsi/scsi_message.h> /* sigh sigh sigh! */
typedef struct cam_device *DEVICE_TYPE;
#endif
...

And there's nothing like these for OpenBSD, and none of these
interfaces seem to exist, so DEVICE_TYPE never gets defined as a
struct, which explains why the compilation fails, citing DEVICE_TYPE as
it's error...

Does anyone have any other suggestions? Knowledge of an OpenBSD
version of MTX? What I can do to make it compile?

Gaby

--
Uganda Maximum - Enemy of the English Thrust
gaby < at > vanhegan.net
http://weblog.vanhegan.net

On Wednesday 14 July 2004 08:45, Gaby Vanhegan wrote:
Hi,

First of all, I'd like to apologise for the cross post, but this has
been knacking me off for 2 weeks now, and I really want to get this
sorted... :)

Having some minor issues with Amanda on OpenBSD3.4, talking to a
Dell Powervault 120T 7-slot changer/drive. After eventually
working my way through the changer scripts I've found that chg-chio
is the one for me. chg-scsi, couldn't figure out the configuration
files and couldn't take to the jukebox, but chg-chio, using the
chio program works fine.

The issue that I have now is that I'm finding amtape unreliable at
moving tapes around effectively, and also that it's having problems
rewinding tapes. I don't know if this is an OpenBSD related issue
or an Amanda issue. I'm using the latest release version that I
could find on the site (amanda-2.4.4p3) compiled from source.

Using chio to move tapes between slots works perfectly, so I don't
think it's a changer issue, and I can't find any mention of the
error messages in the changer code. It looks like it's having some
issues with regards to rewinding the tapes, and not handling the
time that the tape would take to rewind. In my configuration, it
seems that the taper has no method of handling the fact that the
drive is not ready, and just returns a file handle open error on
/dev/nrst0. I suppose that I would either need to know how to get
the Dell Powervault 120T working under the chg-scsi driver, or some
means of adding a delay into the process to allow the drive to
ready itself before letting ammt get anywhere near /dev/nrst0.

My configuration is called ltsn. Here is an example of what happens
when changing a tape around:

bash-2.05b# /usr/local/sbin/amtape ltsn slot first
amtape: could not rewind /dev/nrst0: tape_rewind: tape open:
/dev/nrst0: Input/output erroramtape: changed to slot 1 on
/dev/nrst0

bash-2.05b# cat /tmp/amanda/amtape.20040714123758.debug
amtape: debug 1 pid 30456 ruid 0 euid 0: start at Wed Jul 14
12:37:58 2004 changer: got exit: 0 str: 2 /dev/nrst0
amtape: pid 30456 finish time Wed Jul 14 12:39:05 2004

bash-2.05b# cat /tmp/amanada/changer.debug
Wed Jul 14 12:43:30 2004: enter: getTapeParams
Wed Jul 14 12:43:30 2004: running: /bin/chio -f /dev/ch0 params
Wed Jul 14 12:43:30 2004: /dev/ch0: 7 slots, 1 drive, 1 picker
Wed Jul 14 12:43:30 2004: /dev/ch0: current picker: 0
Wed Jul 14 12:43:30 2004: leave: getTapeParams: 7, 1, 1
Wed Jul 14 12:43:30 2004: enter: getTapeStatus
Wed Jul 14 12:43:30 2004: running: /bin/chio -f /dev/ch0 status
Wed Jul 14 12:43:31 2004: picker 0:
Wed Jul 14 12:43:31 2004: slot 0: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: slot 1: <ACCESS>
Wed Jul 14 12:43:31 2004: slot 2: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: slot 3: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: slot 4: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: slot 5: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: slot 6: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: drive 0: <ACCESS,FULL>
Wed Jul 14 12:43:31 2004: enter: getCurrentTape
Wed Jul 14 12:43:31 2004: leave: getCurrentTape: 2
Wed Jul 14 12:43:31 2004: leave: getTapeStatus: 7
Wed Jul 14 12:43:31 2004MT -> /usr/local/sbin/ammt -f /dev/nrst0
rewind Wed Jul 14 12:43:31 2004: enter: changeTape: 1
Wed Jul 14 12:43:31 2004: enter: Unload: 2
Wed Jul 14 12:44:13 2004: leave: Unload
Wed Jul 14 12:44:13 2004: enter: Load: 1
Wed Jul 14 12:44:13 2004: running: /bin/chio -f /dev/ch0 move slot 0
drive 0 Wed Jul 14 12:44:37 2004: leave: Load
Wed Jul 14 12:44:37 2004: leave: changeTape
Wed Jul 14 12:44:37 2004: 1 /dev/nrst0

bash-2.05b# chio status
picker 0:
slot 0: <ACCESS>
slot 1: <ACCESS,FULL>
slot 2: <ACCESS,FULL>
slot 3: <ACCESS,FULL>
slot 4: <ACCESS,FULL>
slot 5: <ACCESS,FULL>
slot 6: <ACCESS,FULL>
drive 0: <ACCESS,FULL>

Whilst the drive is not ready, this message appears in the dmesg:

st0(ahc1:3:0): Check Condition on opcode 0x0
SENSE KEY: Not Ready
ASC/ASCQ: Logical Unit Is in Process Of Becoming Ready

And ammt returns this:

bash-2.05b# /usr/local/sbin/ammt -d -f /dev/nrst0 status
debug mode!
syntax: eof -> e
syntax: weof -> w
syntax: fsf -> f
syntax: asf -> a
syntax: bsf -> b
syntax: rewind -> rewi
syntax: offline -> o
syntax: rewoffl -> rewo
syntax: status -> s
tapename is "/dev/nrst0"
calling tape_open("/dev/nrst0",0)
/dev/nrst0 status failed: Input/output error

Eventually, the tape comes online and can be used, after about 30
seconds:

bash-2.05b# /usr/local/sbin/ammt -d -f /dev/nrst0 status
debug mode!
syntax: eof -> e
syntax: weof -> w
syntax: fsf -> f
syntax: asf -> a
syntax: bsf -> b
syntax: rewind -> rewi
syntax: offline -> o
syntax: rewoffl -> rewo
syntax: status -> s
tapename is "/dev/nrst0"
calling tape_open("/dev/nrst0",0)
processing status(1)
calling tapefd_status()
/dev/nrst0 status: ONLINE ds == 0x0003 er == 0x0000

Gaby

This is the same problem that has bugged me for 2-3 years,
its been mentioned on this list several times, and generally
ignored.

I used chg-scsi, which isn't that hard to setup, and it
worked when the drive worked (mine died about a month back
and has not been replaced, but will be, with dvd-+rw eventually),
except for rewinding, if I had run amcheck in order to
make it load the right tape beforehand, then I had to
cron-script a rewind command using mt before the amdump
session started since amcheck reads the label and leaves it
sitting at block 1 when its done. If it was sitting on block 1,
then amdump never tried to rewind it, it just read the next block,
not finding the label, so it went into degraded mode.

This was also true of amcheck, if the tape it wanted was
loaded, mt must be used to rewind it before amcheck was
run else the lack of a functioning rewind caused it to
error and cycle thru to the next tape, trying the rest
of the magazine and finding all those labels just fine,
but not recheck the one it started on. A re-run of
amcheck would then find the label correctly
because the act of ejecting the tape forces the _drive_
to rewind before it ejects. Then, when that tape is
reloaded, the label is found correctly, but is not
rewound, and this must be done by mt before the amdump
run starts else amdump gets a tummy ache, as noted above.

I consider it a bug, of VERY long standing duration.

Now, the confusion in setting up chg-scsi seems to be mainly
centered around how you specify the tape device, both in
amanda.conf and in chg-scsi.conf. Or at least that was the
source of my confusion early on.

If useing chg-scsi, then the tape device in the amanda.conf is
specified by a number, not a device, and this number is used to
lookup that profile in chg-scsi.conf. chg-scsi.conf can hold
more than one drives profile, starting with a base zero 0.

Some applicable snippets from my amanda.conf:
------------
autoflush yes

# At most one changerfile entry must be defined; select the most
# appropriate one for your configuration. If you select man-changer,
# keep the first one; if you decide not to use a tape changer, you may
# comment them all out.

runtapes 1 # number of tapes to be used in a single run of amdump
tpchanger "chg-scsi" # the tape-changer glue script
tapedev "0" # the no-rewind tape device to be used
changerfile "/usr/local/etc/amanda/DailySet1/chg-scsi.conf"
tapetype DDS2 # what kind of tape it is (see tapetypes below)
amrecover_do_fsf yes # amrecover will call amrestore with the
# -f flag for faster positioning of the tape.
amrecover_check_label yes # amrecover will call amrestore with the
# -l flag to check the label.
amrecover_changer "chg-scsi" # amrecover will use the changer if you restore
#amrecover_changer "chg-mtx" # from this device.
----
And I'll leave this in as it formats your reports much nicer than
the stock entry for columnspec:
----
# The format for a ColumnSpec is a ',' seperated list of triples.
# Each triple consists of
# + the name of the column (as in ColumnNameStrings)
# + prefix before the column
# + the width of the column, if set to -1 it will be recalculated
# to the maximum length of a line to print.
# Example:
# "Disk=1:17,HostName=1:10,OutKB=1:7"
# or
# "Disk=1:-1,HostName=1:10,OutKB=1:7"
#
# You need only specify those colums that should be changed from
# the default. If nothing is specified in the configfile, the
# above compiled in values will be in effect, resulting in an
# output as it was all the time.
# The names of the colums are:
# HostName, Disk, Level, OrigKB, OutKB, Compress, DumpTime, DumpRate,
# TapeTime and TapeRate.
# ElB, 1999-02-24.
# Warning, one loooong line.
columnspec "Disk=1:18,HostName=0:10,Level=1:3,OrigKB=1:9,OutKB=1:9,Compress=1:7,DumpTime=1:7,DumpRate=1:7,TapeTime=1:7,TapeRate=1:7"


As follows from my chg-scsi.conf for a ctl-96 drive which has
only one profile:
-------------
number_configs 1
eject 0 # Tapedrives need an eject command
sleep 60 # Seconds to wait until the tape gets ready
cleanmax 100 # How many times could a cleaning tape get used
scsitapedev /dev/sg0 # test entry per Jean-Louis request
changerdev /dev/sg1
debuglevel 9:0
#
# Next comes the data for drive 0
#
config 0 #<--this is the tapedev 0 in amanda.conf
drivenum 0
dev /dev/nst0 # the device that is used for the tapedrive 0
startuse 0 # The slots associated with the drive 0
enduse 3 #
statfile /usr/local/etc/amanda/tape-slot # The file where the actual slot is stored
#cleancart 3 # the slot where the cleaningcartridge for drive 0 is located
#cleanfile /usr/local/etc/amanda/tape-clean # The file where the cleanings are recorded
usagecount /usr/local/etc/amanda/totaltime

# This is the end
------------------

Hopefully, this will clarify things a wee bit.

--
Cheers, Gene
There are 4 boxes to be used in defense of liberty.
Soap, ballot, jury, and ammo.
Please use in that order, starting now. -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004,
Maurice E. Heskett, all rights reserved.

On 14 Jul 2004, at 16:48, Gene Heskett wrote:

Now, the confusion in setting up chg-scsi seems to be mainly
centered around how you specify the tape device, both in
amanda.conf and in chg-scsi.conf. Or at least that was the
source of my confusion early on.

OK, having looked at your files and changed my own, I'm still no
closer. I now get this:

bash-2.05b# sudo -u operator /usr/local/sbin/amcheck ltsn
Amanda Tape Server Host Check
-----------------------------
Holding disk /home/amanda/holding: 47180616 KB disk space available,
that's plenty
amcheck-server: could not get changer info: open: /dev/ch0: Bad file
descriptor

Can anyone see any problems with these rrelevant portions of
amanda.conf:

runtapes 1 # number of tapes to be used in a single run of
amdump
tpchanger "chg-scsi" # the tape-changer glue script
tapedev "0" # the no-rewind tape device to be used
rawtapedev "/dev/null" # the raw device to be used (ftape only)
changerfile "/usr/local/etc/amanda/ltsn/chg-scsi.conf"
#changerdev "/dev/ch0"

maxdumpsize -1 # Maximum number of bytes the planner will
schedule
# for a run (default: runtapes * tape_length).
tapetype DLT # what kind of tape it is (see tapetypes below)
labelstr "^ltsn[0-9][0-9]*$" # label constraint regex: all tapes
must match

amrecover_do_fsf yes # amrecover will call amrestore with the
# -f flag for faster positioning of the
tape.
amrecover_check_label yes # amrecover will call amrestore with the
# -l flag to check the label.
amrecover_changer "chg-scsi" # amrecover will use the changer if you
restore
# from this device.
# It could be a string like 'changer'
and
# amrecover will use your changer if you
# set your tape with 'settape changer'

And chg-scsi.conf:

# chg-scsi for Dell Power Vault 120T
number_configs 1 # Only 1 configuration

eject 1 # Tapedrives need an eject command
sleep 90 # Seconds to wait until the tape gets ready
cleanmax 100 # How many times could a cleaning tape get
used
debug 9:0 # High debug level please
scsitapedev /dev/nrst0 # Non-rewinding tape device
changerdev /dev/ch0 # Jukebox changer

# Configuration 0
config 0 # ID for this configuration
drivenum 0 # Use drive id 0
dev /dev/nrst0 # the device that is used for the tapedrive
0
startuse 0 # The slots associated with the drive 0
enduse 6 # Final slot to use
statfile /usr/local/etc/amanda/ltsn/chg-scsi-slot # The file
where the actual slot is stored
usagecount /usr/local/etc/amanda/ltsn/totaltime #
Statistics file

Gaby

--
Uganda Maximum - Enemy of the English Thrust
gaby < at > vanhegan.net
http://weblog.vanhegan.net

On Wednesday 14 July 2004 14:16, Gaby vanhegan wrote:
On 14 Jul 2004, at 16:48, Gene Heskett wrote:
Now, the confusion in setting up chg-scsi seems to be mainly
centered around how you specify the tape device, both in
amanda.conf and in chg-scsi.conf. Or at least that was the
source of my confusion early on.

OK, having looked at your files and changed my own, I'm still no
closer. I now get this:

bash-2.05b# sudo -u operator /usr/local/sbin/amcheck ltsn
Amanda Tape Server Host Check
-----------------------------
Holding disk /home/amanda/holding: 47180616 KB disk space available,
that's plenty
amcheck-server: could not get changer info: open: /dev/ch0: Bad file
descriptor

I'm assuming that your ltsn config lives in /usr/local/etc/ltsn?
Just making sure this is the same amanda.conf that amanda is using :)

Can anyone see any problems with these rrelevant portions of
amanda.conf:

runtapes 1 # number of tapes to be used in a single run
of amdump
tpchanger "chg-scsi" # the tape-changer glue script
tapedev "0" # the no-rewind tape device to be used
rawtapedev "/dev/null" # the raw device to be used (ftape only)
^^^^^^^^^
The above item should be commented out. Don't know if thats the cause
of the problem though.

changerfile "/usr/local/etc/amanda/ltsn/chg-scsi.conf"
#changerdev "/dev/ch0"

maxdumpsize -1 # Maximum number of bytes the planner will
schedule
# for a run (default: runtapes *
tape_length). tapetype DLT # what kind of tape it is
(see tapetypes below) labelstr "^ltsn[0-9][0-9]*$" # label
constraint regex: all tapes must match

amrecover_do_fsf yes # amrecover will call amrestore with
the # -f flag for faster positioning of the tape.
amrecover_check_label yes # amrecover will call amrestore with
the # -l flag to check the label. amrecover_changer "chg-scsi" #
amrecover will use the changer if you restore
# from this device.
# It could be a string like
'changer' and
# amrecover will use your changer
if you # set your tape with 'settape changer'

And chg-scsi.conf:

# chg-scsi for Dell Power Vault 120T
number_configs 1 # Only 1 configuration

eject 1 # Tapedrives need an eject command
sleep 90 # Seconds to wait until the tape gets
ready cleanmax 100 # How many times could a cleaning
tape get used
debug 9:0 # High debug level please
scsitapedev /dev/nrst0 # Non-rewinding tape device
changerdev /dev/ch0 # Jukebox changer
Ahh, here be dragons^^^^

Substitute for /dev/ch0, whatever your dmesg (boot log) identifies the
changer mechanism as. I'll insert the pieces from mine for an
example of what to look for. Unforch, its for linux_x86 here, so the
actual device names are going to be different.

# Configuration 0
config 0 # ID for this configuration
drivenum 0 # Use drive id 0
dev /dev/nrst0 # the device that is used for the
tapedrive 0
startuse 0 # The slots associated with the drive 0
enduse 6 # Final slot to use
statfile /usr/local/etc/amanda/ltsn/chg-scsi-slot # The
file where the actual slot is stored
usagecount /usr/local/etc/amanda/ltsn/totaltime #
Statistics file

Gaby

From my dmesg:
-------
scsi0 : AdvanSys SCSI 3.4MGH: PCI Ultra: IO 0xD000-0xD00F, IRQ 0xB
Vendor: ARCHIVE Model: Python 28849-XXX Rev: 4.CM
Type: Sequential-Access ANSI SCSI revision: 02
Vendor: ARCHIVE Model: Python 28849-XXX Rev: 4.CM
Type: Medium Changer ANSI SCSI revision: 02
st: Version 20030622, fixed bufsize 32768, s/g segs 256
Attached scsi tape st0 at scsi0, channel 0, id 1, lun 0
st0: try direct i/o: yes, max page reachable by HBA 131056
Attached scsi generic sg0 at scsi0, channel 0, id 1, lun 0, type 1
Attached scsi generic sg1 at scsi0, channel 0, id 1, lun 1, type 8
-----
This last item is the changer robot portion of this particular drive,
so the changer then is addressed as /dev/sg1 in this case.

Note too, that its the same base scsi address as the drive, but is at
"lun 1". If you were running a redhat kernel, you would have to
rebuild it after turning the SCAN_ALL_LUNS in the .config file,
otherwise the changer itself will not be found at noot time. The
SCAN_ALL_LUNS makes the boot a bit slower since in a scsi2 narrow
environment, there are still 43 potential devices it has to query
rather than 7 for the usual case.

This should help. Yelp to this list if it doesn't.

--
Cheers, Gene
There are 4 boxes to be used in defense of liberty.
Soap, ballot, jury, and ammo.
Please use in that order, starting now. -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004,
Maurice E. Heskett, all rights reserved.

On 15 Jul 2004, at 03:31, Gene Heskett wrote:

bash-2.05b# sudo -u operator /usr/local/sbin/amcheck ltsn
Amanda Tape Server Host Check
-----------------------------
Holding disk /home/amanda/holding: 47180616 KB disk space available,
that's plenty
amcheck-server: could not get changer info: open: /dev/ch0: Bad file
descriptor

I'm assuming that your ltsn config lives in /usr/local/etc/ltsn?
Just making sure this is the same amanda.conf that amanda is using :)

Almost, it's all inside /usr/local/etc/amanda/ltsn

rawtapedev "/dev/null" # the raw device to be used (ftape only)
^^^^^^^^^
The above item should be commented out. Don't know if thats the cause
of the problem though.

I'll try it, but I don't think it's the issue.

changerdev /dev/ch0 # Jukebox changer
Ahh, here be dragons^^^^

Substitute for /dev/ch0, whatever your dmesg (boot log) identifies the
changer mechanism as. I'll insert the pieces from mine for an
example of what to look for. Unforch, its for linux_x86 here, so the
actual device names are going to be different.

From my own dmesg:

ahc1 at pci0 dev 14 function 0 "Adaptec AHA-2940U2 U2" rev 0x00: irq 10
ahc1: aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/255 SCBs
scsibus1 at ahc1: 16 targets
(ahc1:A:1:0): refuses WIDE negotiation. Using 8bit transfers
ahc1: target 1 using asynchronous transfers
ch0 at scsibus1 targ 1 lun 0: <ADIC, FastStor DLT, D118> SCSI2
8/changer removable
ahc1: target 3 synchronous at 10.0MHz, offset = 0xf
st0 at scsibus1 targ 3 lun 0: <BNCHMARK, DLT1, 3213> SCSI2 1/sequential
removable
st0: density code 0x40, variable blocks, write-enabled

I'm running OpenBSD here, and it identifies changers in the ch driver,
therefore my changer is /dev/ch0

The only problem now is that I had to reboot the machine last night,
due to a routing issue, and now my tape drive is in some wierd state:

bash-2.05b# chio status
picker 0: <EXCEPT>
slot 0: <ACCESS,EXCEPT>
slot 1: <ACCESS,EXCEPT,FULL>
slot 2: <ACCESS,EXCEPT,FULL>
slot 3: <ACCESS,EXCEPT,FULL>
slot 4: <ACCESS,EXCEPT,FULL>
slot 5: <ACCESS,EXCEPT,FULL>
slot 6: <ACCESS,EXCEPT,FULL>
drive 0: <ACCESS,EXCEPT,FULL>

And I can't get it out of that. I think I need to power cycle the lot
of it, which will have to wait until monday when I can get at the
machinery... :(

Gaby

--
Uganda Maximum - Enemy of the English Thrust
gaby < at > vanhegan.net
http://weblog.vanhegan.net

On Thursday 15 July 2004 06:18, Gaby vanhegan wrote:
On 15 Jul 2004, at 03:31, Gene Heskett wrote:
bash-2.05b# sudo -u operator /usr/local/sbin/amcheck ltsn
Amanda Tape Server Host Check
-----------------------------
Holding disk /home/amanda/holding: 47180616 KB disk space
available, that's plenty
amcheck-server: could not get changer info: open: /dev/ch0: Bad
file descriptor

I'm assuming that your ltsn config lives in /usr/local/etc/ltsn?
Just making sure this is the same amanda.conf that amanda is using
:)

Almost, it's all inside /usr/local/etc/amanda/ltsn

Yeah, I'd forgotten the 'amanda' above. My bad.

rawtapedev "/dev/null" # the raw device to be used (ftape only)

^^^^^^^^^
The above item should be commented out. Don't know if thats the
cause of the problem though.

I'll try it, but I don't think it's the issue.

Well, there are explicite instructions that only one device may be
active at a time there.

changerdev /dev/ch0 # Jukebox changer

Ahh, here be dragons^^^^

Substitute for /dev/ch0, whatever your dmesg (boot log) identifies
the changer mechanism as. I'll insert the pieces from mine for an
example of what to look for. Unforch, its for linux_x86 here, so
the actual device names are going to be different.

From my own dmesg:

ahc1 at pci0 dev 14 function 0 "Adaptec AHA-2940U2 U2" rev 0x00: irq
10 ahc1: aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/255 SCBs
scsibus1 at ahc1: 16 targets
(ahc1:A:1:0): refuses WIDE negotiation. Using 8bit transfers
ahc1: target 1 using asynchronous transfers
ch0 at scsibus1 targ 1 lun 0: <ADIC, FastStor DLT, D118> SCSI2
8/changer removable
ahc1: target 3 synchronous at 10.0MHz, offset = 0xf
st0 at scsibus1 targ 3 lun 0: <BNCHMARK, DLT1, 3213> SCSI2
1/sequential removable
st0: density code 0x40, variable blocks, write-enabled

I'm running OpenBSD here, and it identifies changers in the ch
driver, therefore my changer is /dev/ch0

I see that. But I also see that the normal addressing convention isn't
used, as its scsi address 1 and the drive is scsi address 3. Odd,
and I wonder why they skipped 2, and why the changer is first,
normally its second. Are the addresses individually jumperable? Not
that I think thats the problem, but it might be worth keeping notes.

The only problem now is that I had to reboot the machine last night,
due to a routing issue, and now my tape drive is in some wierd
state:

bash-2.05b# chio status
picker 0: <EXCEPT>
slot 0: <ACCESS,EXCEPT>
slot 1: <ACCESS,EXCEPT,FULL>
slot 2: <ACCESS,EXCEPT,FULL>
slot 3: <ACCESS,EXCEPT,FULL>
slot 4: <ACCESS,EXCEPT,FULL>
slot 5: <ACCESS,EXCEPT,FULL>
slot 6: <ACCESS,EXCEPT,FULL>
drive 0: <ACCESS,EXCEPT,FULL>

And I can't get it out of that. I think I need to power cycle the
lot of it, which will have to wait until monday when I can get at
the machinery... :(

Yuck... Good luck.


Gaby

--
Cheers, Gene
There are 4 boxes to be used in defense of liberty.
Soap, ballot, jury, and ammo.
Please use in that order, starting now. -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004,
Maurice E. Heskett, all rights reserved.