Stefan,
I didn't realize the amlabel command wrote a log, I have it,
unfortunately not as informative as one might like in these
circumstances.
samar 5# more amlabel.20080229105753.debug
amlabel: debug 1 pid 873486 ruid 0 euid 0: start at Fri Feb 29 10:57:53 2008
amlabel: writing label: Invalid argument
amlabel: pid 873486 finish time Fri Feb 29 10:57:53 2008
The change from the jukebox to the standalone drive involved
these changes to amanda.conf.
samar 11# diff amanda.conf amanda.conf-20080221-jukebox
93,95c93,94
< #runtapes 2 # number of tapes to be used in a single run of amdump
< runtapes 1 # number of tapes to be used in a single run of amdump
< #tpchanger "chg-zd-mtx" # the tape-changer glue script
---
> runtapes 2 # number of tapes to be used in a single run of amdump
> tpchanger "chg-zd-mtx" # the tape-changer glue script
97,98c96
< #tapedev "/dev/sdlt2" # the no-rewind tape device to be used
< tapedev "/dev/sdlt" # the no-rewind tape device to be used
---
> tapedev "/dev/sdlt2" # the no-rewind tape device to be used
101,102c99,100
< #changerfile "/usr5/amanda/chg-zd-mtx"
< #changerdev "/dev/scsi/sc7d1l0"
---
> changerfile "/usr5/amanda/chg-zd-mtx"
> changerdev "/dev/scsi/sc7d1l0"
Apparently I didn't change the tape type, I probably should have
but I don't know that the tapes differ except for capacity as the
current drive is an SDLT 220.
samar 13# mt -f /dev/sdlt status
Controller: SCSI
Device: QUANTUM: SuperDLT1 3737?7
Status: 0x20262
Drive type: unknown
Media : READY, writable, at BOT
samar 14# mt -f /dev/sdlt2 status
Controller: SCSI
Device: QUANTUM: SDLT320 3838?8
Status: 0xa00
Drive type: unknown
Media : Not READY
>From amanda.conf, the tapetype definition. Nothing terribly odd
here I don't think.
define tapetype SDLT {
comment "QUAMTUM SDLT320"
length 160000 mbytes
filemark 100 kbytes # don't know a better value
speed 100 kbytes # dito
}
And again, I was able to label and write the first several tapes
without addititional changes to the config.
I was also unable to dump or tar to the drive, I wonder if we
don't have a general failure.
I will ask a user to see if they can access the drive properly
with whatever tapes they normally use in this drive (it was used
for user data archiving before I commendeered it.
thanks,
Brian
On Fri, Feb 29, 2008 at 09:57:07AM +0100, Stefan G. Weichinger wrote:
> Brian Cuttler schrieb:
> > Hello Amanda users,
> >
> > I had the jukebox I use on one of my SGI/IRIX Amanda servers fail
> > and we reverted to the attached standalone SDLT 220.
> >
> > I modified amanda.conf to use the different tape drive and to
> > not use any changer config.
> >
> > I was able to label (one/day) a few tapes (and write them that evening),
> > but I'm having difficulty with subsequent tapes.
> >
> > samar 8# /usr/local/sbin/amlabel -f samar SAMAR30
> > rewinding, reading label, reading label: Invalid argument
> > rewinding, writing label SAMAR30
> > amlabel: writing label: Invalid argument
>
> So you use another tapetype.
> What does it look like? Any specific settings in there?
> Using some unusual blocksize or something?
>
> Also browse the log- and debugfiles for anything related.
>
> Stefan
---
Brian R Cuttler [EMAIL PROTECTED]
Computer Systems Support (v) 518 486-1697
Wadsworth Center (f) 518 473-6384
NYS Department of Health Help Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure. It
is intended only for the addressee. If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments. Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
