Backup Central

Hi,

When I run amcheck with chg-scsi, I've got the following message:

Amanda Tape Server Host Check
-----------------------------
Holding disk /data/amanda: 24318827 KB disk space available, that's plenty
amcheck-server: slot 0: tape_rdlabel: tape open: /dev/st0: Input/output error
Jun 21 16:05:30 typha /netbsd: st0: 32768-byte tape record too big for
2048-byte user buffer
Jun 21 16:05:30 typha /netbsd: st0(ahd1:0:1:0): Check Condition on CDB: 0x08
00 00 08 00 00
Jun 21 16:05:30 typha /netbsd: SENSE KEY: No Additional Sense
Jun 21 16:05:30 typha /netbsd: Incorrect Length Indicator Set
Jun 21 16:05:30 typha /netbsd: INFO FIELD: -30720
Jun 21 16:05:30 typha /netbsd: ASC/ASCQ: No Additional Sense Information
Jun 21 16:05:30 typha /netbsd:
amcheck-server: slot 1: reading label: Input/output error
Jun 21 16:05:40 typha /netbsd: st0(ahd1:0:1:0): Check Condition on CDB: 0x15
00 00 00 0c 00
Jun 21 16:05:40 typha /netbsd: SENSE KEY: Not Ready
Jun 21 16:05:40 typha /netbsd: ASC/ASCQ: ASC 0x04 ASCQ 0x07
Jun 21 16:05:40 typha /netbsd:
Jun 21 16:05:40 typha /netbsd: st0: WARNING: cannot revert to default density
Jun 21 16:05:43 typha /netbsd: st0: 32768-byte tape record too big for
2048-byte user buffer
Jun 21 16:05:43 typha /netbsd: st0(ahd1:0:1:0): Check Condition on CDB: 0x08
00 00 08 00 00
Jun 21 16:05:43 typha /netbsd: SENSE KEY: No Additional Sense
Jun 21 16:05:43 typha /netbsd: Incorrect Length Indicator Set
Jun 21 16:05:43 typha /netbsd: INFO FIELD: -30720
Jun 21 16:05:43 typha /netbsd: ASC/ASCQ: No Additional Sense Information
Jun 21 16:05:43 typha /netbsd:
Jun 21 16:05:46 typha /netbsd: ahd1: ahd_handle_ign_wide_residue
Jun 21 16:07:09 typha /netbsd: st0(ahd1:0:1:0): Check Condition on CDB: 0x15
00 00 00 0c 00
Jun 21 16:07:09 typha /netbsd: SENSE KEY: Not Ready
Jun 21 16:07:09 typha /netbsd: ASC/ASCQ: ASC 0x04 ASCQ 0x07
Jun 21 16:07:10 typha /netbsd:
Jun 21 16:07:10 typha /netbsd: st0: WARNING: cannot revert to default density
Jun 21 16:07:17 typha /netbsd: st0: 32768-byte tape record too big for
2048-byte user buffer
Jun 21 16:07:17 typha /netbsd: st0(ahd1:0:1:0): Check Condition on CDB: 0x08
00 00 08 00 00
Jun 21 16:07:17 typha /netbsd: SENSE KEY: No Additional Sense
Jun 21 16:07:17 typha /netbsd: Incorrect Length Indicator Set
Jun 21 16:07:17 typha /netbsd: INFO FIELD: -30720
Jun 21 16:07:17 typha /netbsd: ASC/ASCQ: No Additional Sense Information
Jun 21 16:07:17 typha /netbsd:
amcheck-server: slot 2: reading label: Input/output error
...


All of my tapes are labeled and here is my chg-scsi.conf file

number_configs 1
eject 0
sleep 5
cleanmax 10
scsitapedev /dev/st0
changerdev /dev/ch0
tapestatus /usr/pkg/etc/amanda/backup/changer/status
labelfile /usr/pkg/etc/amanda/backup/changer/label
debuglevel 9:0

config 0
drivenum 0
dev /dev/st0
startuse 0
enduse 9
statfile /usr/pkg/etc/amanda/backup-scsi/changer/statfile
cleancart 57
cleanfile /usr/pkg/etc/amanda/backup/changer-scsi/tape0-clean
usagecount /usr/pkg/etc/amanda/backup/changer-scsi/totaltime

I have defined tapetype in amanda.conf as follows:

define tapetype Fujitsu {
comment "Fujitsu tape"
length 200gbytes
filemark 100kbytes
speed 100 kbytes
}

I don't know why I got that problem. The chg-scsi.debug file (see the attached)
doesn't give me any clue. I would appreciate if anyone could help me to resolve
it.
Thank you,

Co Ngo

cngo < at > nmsu.edu writes:
- When I run amcheck with chg-scsi, I've got the following message:
-
- Amanda Tape Server Host Check
- -----------------------------
- Holding disk /data/amanda: 24318827 KB disk space available, that's plenty
-
- amcheck-server: slot 0: tape_rdlabel: tape open: /dev/st0: Input/output error

On netbsd, /dev/st0 is certainly the wrong device to be
using. You want to use /dev/nrst0.

- All of my tapes are labeled and here is my chg-scsi.conf file
-
- number_configs 1
- eject 0
- sleep 5
- cleanmax 10
- scsitapedev /dev/st0
- changerdev /dev/ch0
- tapestatus /usr/pkg/etc/amanda/backup/changer/status
- labelfile /usr/pkg/etc/amanda/backup/changer/label
- debuglevel 9:0
-
- config 0
- drivenum 0
- dev /dev/st0
- startuse 0
- enduse 9
- statfile /usr/pkg/etc/amanda/backup-scsi/changer/statfile
- cleancart 57
- cleanfile /usr/pkg/etc/amanda/backup/changer-scsi/tape0-clean
- usagecount /usr/pkg/etc/amanda/backup/changer-scsi/totaltime

This should look more like this:


number_configs 1
eject 0
sleep 5
cleanmax 10
changerdev /dev/ch0
tapestatus /usr/pkg/etc/amanda/backup/changer/status
labelfile /usr/pkg/etc/amanda/backup/changer/label
debuglevel 9:0

config 0
drivenum 0
dev /dev/nrst0
scsitapedev /dev/enrst0
startuse 0
enduse 9
statfile /usr/pkg/etc/amanda/backup-scsi/changer/statfile
cleancart 57
cleanfile /usr/pkg/etc/amanda/backup/changer-scsi/tape0-clean
usagecount /usr/pkg/etc/amanda/backup/changer-scsi/totaltime

FYI: I usually put the `cleanfile', `usagecount', `statfile',
`tapestatus' and `labelfile' files under /var/spool/amanda, to
leave the /usr/pkg clear of frequently modified files.

You might also find some patches I made for use on NetBSD interesting.
They are available at ftp://ftp.cirr.com/pub/utils/amanda. Place
them in a pkgsrc shadow tree (subdirectory sysutils/amanda-server)
and set LOCALPATCHES to the top of the shadow tree, and rebuild.

FYI: I've been running Amanda on NetBSD for 10 years or
so.. Currently running on an AlphaPC64 as a tape server.

--
Eric Schnoebelen eric < at > cirr.com http://www.cirr.com
"Everything is theoretically impossible, until it is done. One could write
a history of science in reverse by assembling the solemn pronouncements of
highest authority about what could not be done and what could never happen."
-- Robert Heinlein

Eric,

Thank you very much for very useful advice. I've change chg-scsi.conf file as
you said. I didn't get the Input/ouput error message. However, I still get the
following errors:

Amanda Tape Server Host Check
-----------------------------
Holding disk /data/amanda: 24318827 KB disk space available, that's plenty
Jun 22 10:04:22 typha last message repeated 39 times
Jun 22 14:39:42 typha /netbsd: st0(ahd1:0:1:0): Check Condition on CDB: 0x15
00 00 00 0c 00
Jun 22 14:39:42 typha /netbsd: SENSE KEY: Not Ready
Jun 22 14:39:42 typha /netbsd: ASC/ASCQ: ASC 0x04 ASCQ 0x07
Jun 22 14:39:42 typha /netbsd:
Jun 22 14:39:42 typha /netbsd: st0: WARNING: cannot revert to default density
amcheck-server: slot 9: date 20040616 label Biology-1 (first labelstr match)
Jun 22 14:39:55 typha /netbsd: st0(ahd1:0:1:0): Check Condition on CDB: 0x15
00 00 00 0c 00
Jun 22 14:39:55 typha /netbsd: SENSE KEY: Not Ready
Jun 22 14:39:55 typha /netbsd: ASC/ASCQ: ASC 0x04 ASCQ 0x07
Jun 22 14:39:55 typha /netbsd:
Jun 22 14:39:55 typha /netbsd: st0: WARNING: cannot revert to default density
Jun 22 14:39:58 typha /netbsd: ahd1: drive (ID 1, LUN 0) queue full (SCB 0xe)
Jun 22 14:39:59 typha /netbsd: ahd1: ahd_handle_ign_wide_residue
Jun 22 14:41:23 typha /netbsd: st0(ahd1:0:1:0): Check Condition on CDB: 0x15
00 00 00 0c 00
Jun 22 14:41:23 typha /netbsd: SENSE KEY: Not Ready
Jun 22 14:41:23 typha /netbsd: ASC/ASCQ: ASC 0x04 ASCQ 0x07
Jun 22 14:41:23 typha /netbsd:
Jun 22 14:41:23 typha /netbsd: st0: WARNING: cannot revert to default density
Jun 22 14:41:30 typha /netbsd: ahd1: drive (ID 1, LUN 0) queue full (SCB 0xe)
amcheck-server: slot 0: date 20040616 label Biology-1 (labelstr match)
Jun 22 14:41:37 typha /netbsd: st0(ahd1:0:1:0): Check Condition on CDB: 0x15
00 00 00 0c 00
Jun 22 14:41:37 typha /netbsd: SENSE KEY: Not Ready
Jun 22 14:41:37 typha /netbsd: ASC/ASCQ: ASC 0x04 ASCQ 0x07
Jun 22 14:41:37 typha /netbsd:
Jun 22 14:41:37 typha /netbsd: st0: WARNING: cannot revert to default density
Jun 22 14:41:41 typha /netbsd: ahd1: drive (ID 1, LUN 0) queue full (SCB 0xe)
Jun 22 14:41:42 typha /netbsd: ahd1: ahd_handle_ign_wide_residue
.....

Do you have any idea about it. BTW, I haven't tried your patches. Kindly have a
look at my amanda.conf and chg-scsi.conf files and give me your advice.

Thank you very much,

Co Ngo


Quoting Eric Schnoebelen <eric < at > cirr.com>:


cngo < at > nmsu.edu writes:
- When I run amcheck with chg-scsi, I've got the following message:
-
- Amanda Tape Server Host Check
- -----------------------------
- Holding disk /data/amanda: 24318827 KB disk space available, that's plenty

-
- amcheck-server: slot 0: tape_rdlabel: tape open: /dev/st0: Input/output
error

On netbsd, /dev/st0 is certainly the wrong device to be
using. You want to use /dev/nrst0.

- All of my tapes are labeled and here is my chg-scsi.conf file
-
- number_configs 1
- eject 0
- sleep 5
- cleanmax 10
- scsitapedev /dev/st0
- changerdev /dev/ch0
- tapestatus /usr/pkg/etc/amanda/backup/changer/status
- labelfile /usr/pkg/etc/amanda/backup/changer/label
- debuglevel 9:0
-
- config 0
- drivenum 0
- dev /dev/st0
- startuse 0
- enduse 9
- statfile /usr/pkg/etc/amanda/backup-scsi/changer/statfile
- cleancart 57
- cleanfile /usr/pkg/etc/amanda/backup/changer-scsi/tape0-clean
- usagecount /usr/pkg/etc/amanda/backup/changer-scsi/totaltime

This should look more like this:


number_configs 1
eject 0
sleep 5
cleanmax 10
changerdev /dev/ch0
tapestatus /usr/pkg/etc/amanda/backup/changer/status
labelfile /usr/pkg/etc/amanda/backup/changer/label
debuglevel 9:0

config 0
drivenum 0
dev /dev/nrst0
scsitapedev /dev/enrst0
startuse 0
enduse 9
statfile /usr/pkg/etc/amanda/backup-scsi/changer/statfile
cleancart 57
cleanfile /usr/pkg/etc/amanda/backup/changer-scsi/tape0-clean
usagecount /usr/pkg/etc/amanda/backup/changer-scsi/totaltime

FYI: I usually put the `cleanfile', `usagecount', `statfile',
`tapestatus' and `labelfile' files under /var/spool/amanda, to
leave the /usr/pkg clear of frequently modified files.

You might also find some patches I made for use on NetBSD interesting.
They are available at ftp://ftp.cirr.com/pub/utils/amanda. Place
them in a pkgsrc shadow tree (subdirectory sysutils/amanda-server)
and set LOCALPATCHES to the top of the shadow tree, and rebuild.

FYI: I've been running Amanda on NetBSD for 10 years or
so.. Currently running on an AlphaPC64 as a tape server.

--
Eric Schnoebelen eric < at > cirr.com http://www.cirr.com
"Everything is theoretically impossible, until it is done. One could write
a history of science in reverse by assembling the solemn pronouncements of
highest authority about what could not be done and what could never
happen."
-- Robert Heinlein

cngo < at > nmsu.edu writes:
- Thank you very much for very useful advice. I've change chg-scsi.conf
- file as you said. I didn't get the Input/ouput error message.
- However, I still get the following errors:

It looks like the tape device isn't fully recognized.
What device is it? (with full model name/number, please) What
robot is it in?

Also, which version of NetBSD are you using, and on what
processor family?

As a guess, chg-scsi needs to learn about that tape
device type, and how to query it for ready status.

- Do you have any idea about it. BTW, I haven't tried your patches.
- Kindly have a look at my amanda.conf and chg-scsi.conf files and
- give me your advice.

The configuration files look good.


--
Eric Schnoebelen eric < at > cirr.com http://www.cirr.com
If bankers can count, how come they have eight windows and only four tellers?

Hi,

I'm running NetBSD 1.6.1 on Dell Lattitude. Here is the device information.

-------
st0 at scsibus1 target 1 lun 0: <HP, Ultrium 2-SCSI, F45H> tape removable
st0: drive empty
st0: sync (25.00ns offset 127), 16-bit (80.000MB/s) transfers
ch0 at scsibus1 target 6 lun 0: <OVERLAND, NEO Series, 0417> changer removable
ch0: async, 8-bit transfers
ch0: 58 slots, 1 drive, 1 picker, 2 portals
ch0: sync (100.00ns offset 15), 16-bit (20.000MB/s) transfers

-----

Although, I got the message, amdump still runs ok. However, I really want to
get rid off that error message and to make everything works smoothly.

Another thing. When I tried chg-chio, everything is fine. Could you please
advise if I should you chg-scsi or chg-chio. I don't know what the advantages
of chg-scsi is, compared with chg-chio. Is that because, with chg-scsi, you can
create the inventory of tapes ? I've already set emubarcode=1 in the
chg-scsi.conf but I don't see any thing in labelfile and can't find the
inventory anywhere. Any suggestion ?

Thank you very much for your help,

Co Ngo

Quoting Eric Schnoebelen <eric < at > cirr.com>:


cngo < at > nmsu.edu writes:
- Thank you very much for very useful advice. I've change chg-scsi.conf
- file as you said. I didn't get the Input/ouput error message.
- However, I still get the following errors:

It looks like the tape device isn't fully recognized.
What device is it? (with full model name/number, please) What
robot is it in?

Also, which version of NetBSD are you using, and on what
processor family?

As a guess, chg-scsi needs to learn about that tape
device type, and how to query it for ready status.

- Do you have any idea about it. BTW, I haven't tried your patches.
- Kindly have a look at my amanda.conf and chg-scsi.conf files and
- give me your advice.

The configuration files look good.


--
Eric Schnoebelen eric < at > cirr.com http://www.cirr.com
If bankers can count, how come they have eight windows and only four
tellers?

cngo < at > nmsu.edu writes:
- I'm running NetBSD 1.6.1 on Dell Lattitude. Here is the device information.
-
- -------
- st0 at scsibus1 target 1 lun 0: <HP, Ultrium 2-SCSI, F45H> tape removable
- st0: drive empty
- st0: sync (25.00ns offset 127), 16-bit (80.000MB/s) transfers
- ch0 at scsibus1 target 6 lun 0: <OVERLAND, NEO Series, 0417> changer removable
- ch0: async, 8-bit transfers
- ch0: 58 slots, 1 drive, 1 picker, 2 portals
- ch0: sync (100.00ns offset 15), 16-bit (20.000MB/s) transfers
-
- -----
-
- Although, I got the message, amdump still runs ok. However, I really
- want to get rid off that error message and to make everything works
- smoothly.

The Ultrium probably needs a variation of the unload
command sequence, that the chg-scsi generic unload doesn't do..
(this is also true of the Exabyte drives.)

- Another thing. When I tried chg-chio, everything is fine. Could
- you please advise if I should you chg-scsi or chg-chio. I don't
- know what the advantages of chg-scsi is, compared with chg-chio.

I've not done anything with the modern chg-chio. (er,
actually, I updated a chg-chio, but that was several years
ago, and it's since mutated further into chg-scsi.)

- Is that because, with chg-scsi, you can create the inventory of
- tapes?

That's one good reason. Using the barcode reader in the
robot, and it's corresponding mapping between barcodes and
Amanda labels, allows much faster access to individual tapes.

- I've already set emubarcode=1 in the chg-scsi.conf but I
- don't see any thing in labelfile and can't find the inventory
- anywhere. Any suggestion ?

I don't know what ``emubarcode'' does, my system has
``havebarcode'', which I have turned on.. (I wonder, did the
name change between 2.4.2 and 2.4.4? I'm still on 2.4.2,
although I'm starting the upgrade process this afternoon.)

For ``havebarcode'' to be useful, there must be a
working barcode reader in the robot, and the tapes media must have
barcoded physical labels attached to the tape shells. Several
vendors sell the barcodes to attach, and at least one sells
media with the labels already attached.

--
Eric Schnoebelen eric < at > cirr.com http://www.cirr.com
"Cutting the space budget really restores my faith in humanity. It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation." -- Johnny Hart