Re: amcheck ignores vtape changer problem
On Saturday, September 11, 2010 10:31:37 am Gene Heskett did opine: On Friday, September 10, 2010 08:57:23 pm Dustin J. Mitchell did opine: On Fri, Sep 10, 2010 at 8:02 AM, Florian Lengyel florian.leng...@gmail.com wrote: Shouldn't amcheck -m DailySet3 send email if there is a changer problem? I'm told that amcheck does not send the email. Yes, and normally it does, so that's either mistakenly reported or there's a bug of some sort. Dustin I'm not too sure there isn't a buglet here Dustin. I haven't been getting an email from amdump, since installing pclos-2010.7, with the Mailto line in my amanda.conf stating that it is to send the report to g...@coyote.coyote.den. So I went looking in /var/spool/mail, and the gene file is normally empty as kmail reads it and sorts to the correct folders. But there was also an amanda mailfile there, containing the messages that cron emits when it runs the dump. But this is not what amanda sends. Do I need an alias or .forward file someplace? So, where the heck is the mail going? I just changed it to send it to g...@localhost for effect. We'll see if I get a mail tonight. Humm, the manpage doesn't say a thing about quotation marks around that string, so I just took them out, and space separated the two recipients. And we wait And find out it doesn't work. Without the quotes around the mailto string, it upchucks all over itself fails to run. They have been added and last nights backup s/b running now. The manpage doesn't say that mailto needs those. Perhaps that s/b clarified? What I found that accounted for all the missing system mail, was that back on August 15th, there seems to have been an update that must have went aglay, I had found an error message that said it couldn't find the /etc/aliases.db directory. But pclos doesn't use a subdir for that. And I had an /etc/aliases~ file and an /etc/aliases.rpmsave file. So I mv'd it to aliases, then added 2 more lines at the bottom to make sure that gene got amanda's mail. Then I ran newaliases and went to bed. This morning I had an inbox with 196 new messages, most of which were failure reports to Postmaster from localhost, so I believe that this problem is now solved. I should think I'll get 2 now, duplicates, because I have two addresses within the quotes on line 9 of my amanda.conf. If that works, I'll take one out. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) If I love you, what business is it of yours? -- Johann van Goethe
Re: amcheck ignores vtape changer problem
On Sat, Sep 11, 2010 at 9:45 AM, Gene Heskett gene.hesk...@gmail.com wrote: And find out it doesn't work. Without the quotes around the mailto string, it upchucks all over itself fails to run. They have been added and last nights backup s/b running now. The manpage doesn't say that mailto needs those. Perhaps that s/b clarified? All strings in the configuration file need to be quoted - that's at the beginning of the amanda.conf manpage. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: amcheck ignores vtape changer problem
On Fri, Sep 10, 2010 at 2:55 PM, Florian Lengyel florian.leng...@gmail.com wrote: 3. They didn't know--or bother to read--that to recover the files, you list the first couple of lines (they configured a custom compression with bzip2): AMANDA: SPLIT_FILE 20100222 guass.engr.ccny.cuny.edu /home1/skgottipati part 8/ 11 lev 0 comp cust program /bin/tar client_custom_compress /bin/bzip2 To restore, position tape at start of file and run: dd if=tape bs=32k skip=1 | /bin/bzip2 -d | /bin/tar -xpGf - 4. Concatenating split files so that they could be unzipped and extracted with tar seems to present a breathtaking challenge. We'll see how far they get. (I will leave the list out of this, of course.) Again, my apologies for distracting the list with this. I did learn about VTapes--many thanks. Wait, why do they need to do restores by hand? Are they unable to use amrecover? Amfetchdump? Even amrestore? Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: amcheck ignores vtape changer problem
On Saturday, September 11, 2010 01:19:44 pm Dustin J. Mitchell did opine: On Sat, Sep 11, 2010 at 9:45 AM, Gene Heskett gene.hesk...@gmail.com wrote: And find out it doesn't work. Without the quotes around the mailto string, it upchucks all over itself fails to run. They have been added and last nights backup s/b running now. The manpage doesn't say that mailto needs those. Perhaps that s/b clarified? All strings in the configuration file need to be quoted - that's at the beginning of the amanda.conf manpage. Dustin Humph, 'swhat I get for scanning at 500- 1k words per. And the backup worked, but still no email from amanda. I'll take it back down to one name for tonight. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) woot Put *that* in you .sig and smoke it, Knghtbrd. Culus You know he will read this : woot heheheheh.
Re: amcheck ignores vtape changer problem
On Sat, Sep 11, 2010 at 12:54 PM, Dustin J. Mitchell dus...@zmanda.comwrote: On Fri, Sep 10, 2010 at 2:55 PM, Florian Lengyel florian.leng...@gmail.com wrote: They have had to recover by hand -- see below (there was a disk crash of some kind, but I have been unable to elicit precise details). See below for errors AMANDA: SPLIT_FILE 20100222 guass.engr.ccny.cuny.edu /home1/skgottipati part 8/ 11 lev 0 comp cust program /bin/tar client_custom_compress /bin/bzip2 To restore, position tape at start of file and run: dd if=tape bs=32k skip=1 | /bin/bzip2 -d | /bin/tar -xpGf - Wait, why do they need to do restores by hand? Are they unable to use amrecover? Amfetchdump? Even amrestore? Dustin -- Open Source Storage Engineer http://www.zmanda.com These were failing -- here's a quote from an email amadmin DailySet3 find Generate the outputs below and hangs... Warning: no log files found for tape DailySet3-013 written 2010-03-01 Warning: no log files found for tape DailySet3-012 written 2010-03-01 Warning: no log files found for tape DailySet3-011 written 2010-02-25 Warning: no log files found for tape DailySet3-010 written 2010-02-25 Warning: no log files found for tape DailySet3-09 written 2010-02-25 Warning: no log files found for tape DailySet3-08 written 2010-02-25 Warning: no log files found for tape DailySet3-07 written 2010-02-25 Warning: no log files found for tape DailySet3-06 written 2010-02-22 Warning: no log files found for tape DailySet3-05 written 2010-02-22 Also ERRORS The following are the errors I get so far trying to recover these 3 directories...(using amrecover) for grossberg, No index records for disk for specified date (nor earlier dates, I tried) for glasslab/skgottipati , Extracting files using tape drive @DEFAULT_TAPE_DEVICE@ on host guass.engr.ccny.cuny.edu. Load tape DailySet03-025 now Continue [?/Y/n/s/d]? Y Volume labeled 'DailySet03-025' not found. Load tape DailySet03-025 now Continue [?/Y/n/d]? Y Not an amanda tape: Can't open tape device @DEFAULT_TAPE_DEVICE@: No such file or directory Load tape DailySet03-025 now With Amrestore, I get the error Got no header and data from server Also, i have tried amarchiver --list --file 1.guass.engr.ccny.cuny.edu._home1_skgottipati.0 amar_read: Invalid archive header Note:- This tape exist and it seems to contain some form of data in it.
Re: amcheck ignores vtape changer problem
On Sat, Sep 11, 2010 at 3:52 PM, Florian Lengyel florian.leng...@gmail.com wrote: Not an amanda tape: Can't open tape device @DEFAULT_TAPE_DEVICE@: No such Hopefully the error here is pretty obvious. I'm not sure how they managed to get that into their configuration, but it's obviously wrong. With Amrestore, I get the error Got no header and data from server No actual indication of how they invoked amrestore. Did they try amfetchdump? amarchiver --list --file 1.guass.engr.ccny.cuny.edu._home1_skgottipati.0 amar_read: Invalid archive header Dhhh. Did they just randomly guess that amarchiver would do the trick, without even looking at the manpage? It looks like you have some major customer education to do here. Good luck. Dustin -- Open Source Storage Engineer http://www.zmanda.com
amcheck ignores vtape changer problem
Hi, The following is the output of amcheck (version info listed below)--it reports a malformed response from the vtape changer and calls this a changer problem. On the other hand it ends by reporting no problems found and does not send the email address configured to receive notifications that there was a changer problem. Is there a problem, or not? What, if anything, should be done about this? Thank you, FL bac...@guass:~$ amcheck DailySet3 Amanda Tape Server Host Check - Holding disk /home1_data/dumps: 1200095232 KB disk space available, using 1095237632 KB Changer problem: Malformed response from changer -info: 1 at /usr/lib/amanda/perl/Amanda/MainLoop.pm line 359 (expecting tape DailySet3-014 or a new tape) NOTE: info dir /etc/amanda/DailySet3/curinfo/ guass.engr.ccny.cuny.edu/_home1_grossberg does not exist NOTE: it will be created on the next run. NOTE: index dir /etc/amanda/DailySet3/index/ guass.engr.ccny.cuny.edu/_home1_grossberg does not exist NOTE: it will be created on the next run. Server check took 0.653 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 2.038 seconds. 0 problems found. (brought to you by Amanda 2.6.1p1) bac...@guass:~$
Re: amcheck ignores vtape changer problem
On Fri, Sep 10, 2010 at 5:41 AM, Florian Lengyel florian.leng...@gmail.com wrote: The following is the output of amcheck (version info listed below)--it reports a malformed response from the vtape changer and calls this a changer problem. On the other hand it ends by reporting no problems found and does not send the email address configured to receive notifications that there was a changer problem. The no problems found is for the client check, not the server check. Is the exit status 0 or something else? amcheck DailySet3; echo $? Is there a problem, or not? What, if anything, should be done about this? Well, that the changer is failing is a problem. Do you know why that's happening? Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: amcheck ignores vtape changer problem
On Fri, Sep 10, 2010 at 8:02 AM, Florian Lengyel florian.leng...@gmail.com wrote: Shouldn't amcheck -m DailySet3 send email if there is a changer problem? I'm told that amcheck does not send the email. Yes, and normally it does, so that's either mistakenly reported or there's a bug of some sort. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: amcheck ignores vtape changer problem
On Fri, Sep 10, 2010 at 8:29 AM, Dustin J. Mitchell dus...@zmanda.comwrote: On Fri, Sep 10, 2010 at 5:41 AM, Florian Lengyel florian.leng...@gmail.com wrote: The following is the output of amcheck (version info listed below)--it reports a malformed response from the vtape changer and calls this a changer problem. On the other hand it ends by reporting no problems found and does not send the email address configured to receive notifications that there was a changer problem. The no problems found is for the client check, not the server check. Is the exit status 0 or something else? amcheck DailySet3; echo $? Is there a problem, or not? What, if anything, should be done about this? Well, that the changer is failing is a problem. Do you know why that's happening? Dustin I will get back to you with the answers--this isn't my system. I don't have experience with VTapes, so I'm not exactly sure where to check to determine the source of the failure. I'm writing on behalf of someone else regarding a system at another campus. Shouldn't amcheck -m DailySet3 send email if there is a changer problem? I'm told that amcheck does not send the email.
Re: amcheck ignores vtape changer problem
I'm not familiar with vtapes, but in any case their amanda.conf file has dumpcycle 1 day # the number of days in the normal dump cycle runspercycle -1 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 25 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle (not sure why runspercycle is -1) and they have runtapes 5 # number of tapes to be used in a single run of amdump tpchanger chg-disk # the tape-changer glue script tapedev file:/home1_data/backups/DailySet3/slots # the no-rewind tape device to be used changerfile /etc/amanda/DailySet3/changer changerdev @DEFAULT_CHANGER_DEVICE@ The file /etc/amanda/DailySet3/changer does not exist. On Fri, Sep 10, 2010 at 11:34 AM, Florian Lengyel florian.leng...@gmail.com wrote: Hi: I now have access to the backup system and can run my own checks. The report I received that AMANDA does not send email even when amcheck -m DailySet3 indicates a changer error seems to have been mistaken. (I needed access to the system to see for myself what was really going on. I leave aside for the time being the question of who should be receiving the emails--which get left on the AMANDA server and are not being forwarded to someone who can address the error.) After this, I will attempt to figure out why there is a changer error. (Any suggestions would be appreciated.) amcheck -m DailySet3 sends the following email (by the way, echo $? returns 1, as it should) Message 78: From bac...@guass Fri Sep 10 11:27:18 2010 X-Original-To: bac...@guass To: bac...@guass Subject: DailySet3 AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE Date: Fri, 10 Sep 2010 11:27:18 -0400 (EDT) From: bac...@guass (backup) Changer problem: Malformed response from changer -info: 1 at /usr/lib/amanda/perl/Amanda/MainLoop.pm line 359 Amanda Tape Server Host Check - Holding disk /home1_data/dumps: 1200095232 KB disk space available, using 1095237632 KB (expecting tape DailySet3-014 or a new tape) NOTE: info dir /etc/amanda/DailySet3/curinfo/ guass.engr.ccny.cuny.edu/_home1_grossberg does not exist NOTE: it will be created on the next run. NOTE: index dir /etc/amanda/DailySet3/index/ guass.engr.ccny.cuny.edu/_home1_grossberg does not exist NOTE: it will be created on the next run. Server check took 0.658 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 1.210 seconds. 0 problems found. Thanks again, FL On Fri, Sep 10, 2010 at 9:43 AM, Dustin J. Mitchell dus...@zmanda.comwrote: On Fri, Sep 10, 2010 at 8:02 AM, Florian Lengyel florian.leng...@gmail.com wrote: Shouldn't amcheck -m DailySet3 send email if there is a changer problem? I'm told that amcheck does not send the email. Yes, and normally it does, so that's either mistakenly reported or there's a bug of some sort. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: amcheck ignores vtape changer problem
Let me ask another question -- is a selfcheck log generated by amcheck? See below. The person responsible for this system writes On Fri, Sep 10, 2010 at 12:30 PM, ** *** wrote: If I never commented it inmy question would be does amanda do a self check before each dump? Since I have selfcheck log for july 29th -- *From:* Florian Lengyel florian.leng...@gmail.com *To:* ** *Sent:* Friday, September 10, 2010 12:22:09 *Subject:* Re: amcheck ignores vtape changer problem You should have received an email from amcheck when this was in the cron. But I don't see any emails from amcheck. I believe it was never commented in. On Fri, Sep 10, 2010 at 9:43 AM, Dustin J. Mitchell dus...@zmanda.comwrote: On Fri, Sep 10, 2010 at 8:02 AM, Florian Lengyel florian.leng...@gmail.com wrote: Shouldn't amcheck -m DailySet3 send email if there is a changer problem? I'm told that amcheck does not send the email. Yes, and normally it does, so that's either mistakenly reported or there's a bug of some sort. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: amcheck ignores vtape changer problem
On Fri, 10 Sep 2010 11:43:32 -0400 Florian Lengyel florian.leng...@gmail.com wrote: I'm not familiar with vtapes, but in any case their amanda.conf file has dumpcycle 1 day # the number of days in the normal dump cycle runspercycle -1 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 25 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle (not sure why runspercycle is -1) From the amanda.conf man page: A value of -1 means guess the number of runs from the tapelist(5) file, which is the number of tapes used in the last dumpcycle days / runtapes. http://wiki.zmanda.com/man/amanda.conf.5.html and they have runtapes 5 # number of tapes to be used in a single run of amdump tpchanger chg-disk # the tape-changer glue script tapedev file:/home1_data/backups/DailySet3/slots # the no-rewind Is that correct? I have tapedev file:/media/backs/amanda/DailySet1 and a bunch of slot* directories in DailySet1. Reading this, I would expect your slot* directories to be in the subdirectory slots. tape device to be used changerfile /etc/amanda/DailySet3/changer changerdev @DEFAULT_CHANGER_DEVICE@ Odd. On my 2.5.1 configuration, changerdev is set to /dev/null. On my 3.1.0 system it isn't set at all, and it defaults to /dev/null. http://wiki.zmanda.com/man/amanda-changers.7.html The file /etc/amanda/DailySet3/changer does not exist. You may not need it, in which case I'd take it out entirely or give it a dummy value. On one of my systems (2.5.2p1, ancient), my entry points to a non-existent file, in an extant directory. On a 3.1.0 system, I don't have it at all. Both use vtapes. -- Charles Curley /\ASCII Ribbon Campaign Looking for fine software \ /Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com/ \No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
Re: amcheck ignores vtape changer problem
OK thanks for this. I must apologize to the list for the subject line. I suspect that whoever configured their system commented out the amcheck line in their crontab--but I don't have a way of verifying this. I will summarize to the list: 1. An email address that a human would read when a failure occurred needed to be set. I have no idea what happened to the amcheck emails. The AMANDA emails were going to an account no one checked for a few months. 2. The chg-disk device went without being reset for over two months. It needed to be reset so that changer-slot would have a value. (But see 1.) I don't know what caused the changer-slot file to become empty. The command they needed to run was /usr/lib/amanda/chg-disk -reset in their configuration directory. 3. They didn't know--or bother to read--that to recover the files, you list the first couple of lines (they configured a custom compression with bzip2): AMANDA: SPLIT_FILE 20100222 guass.engr.ccny.cuny.edu /home1/skgottipati part 8/ 11 lev 0 comp cust program /bin/tar client_custom_compress /bin/bzip2 To restore, position tape at start of file and run: dd if=tape bs=32k skip=1 | /bin/bzip2 -d | /bin/tar -xpGf - 4. Concatenating split files so that they could be unzipped and extracted with tar seems to present a breathtaking challenge. We'll see how far they get. (I will leave the list out of this, of course.) Again, my apologies for distracting the list with this. I did learn about VTapes--many thanks. FL On Fri, Sep 10, 2010 at 3:35 PM, Charles Curley charlescur...@charlescurley.com wrote: On Fri, 10 Sep 2010 11:43:32 -0400 Florian Lengyel florian.leng...@gmail.com wrote: I'm not familiar with vtapes, but in any case their amanda.conf file has dumpcycle 1 day # the number of days in the normal dump cycle runspercycle -1 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 25 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle (not sure why runspercycle is -1) From the amanda.conf man page: A value of -1 means guess the number of runs from the tapelist(5) file, which is the number of tapes used in the last dumpcycle days / runtapes. http://wiki.zmanda.com/man/amanda.conf.5.html and they have runtapes 5 # number of tapes to be used in a single run of amdump tpchanger chg-disk # the tape-changer glue script tapedev file:/home1_data/backups/DailySet3/slots # the no-rewind Is that correct? I have tapedev file:/media/backs/amanda/DailySet1 and a bunch of slot* directories in DailySet1. Reading this, I would expect your slot* directories to be in the subdirectory slots. tape device to be used changerfile /etc/amanda/DailySet3/changer changerdev @DEFAULT_CHANGER_DEVICE@ Odd. On my 2.5.1 configuration, changerdev is set to /dev/null. On my 3.1.0 system it isn't set at all, and it defaults to /dev/null. http://wiki.zmanda.com/man/amanda-changers.7.html The file /etc/amanda/DailySet3/changer does not exist. You may not need it, in which case I'd take it out entirely or give it a dummy value. On one of my systems (2.5.2p1, ancient), my entry points to a non-existent file, in an extant directory. On a 3.1.0 system, I don't have it at all. Both use vtapes. -- Charles Curley /\ASCII Ribbon Campaign Looking for fine software \ /Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com/ \No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
Re: amcheck ignores vtape changer problem
On Friday, September 10, 2010 08:57:23 pm Dustin J. Mitchell did opine: On Fri, Sep 10, 2010 at 8:02 AM, Florian Lengyel florian.leng...@gmail.com wrote: Shouldn't amcheck -m DailySet3 send email if there is a changer problem? I'm told that amcheck does not send the email. Yes, and normally it does, so that's either mistakenly reported or there's a bug of some sort. Dustin I'm not too sure there isn't a buglet here Dustin. I haven't been getting an email from amdump, since installing pclos-2010.7, with the Mailto line in my amanda.conf stating that it is to send the report to g...@coyote.coyote.den. So I went looking in /var/spool/mail, and the gene file is normally empty as kmail reads it and sorts to the correct folders. But there was also an amanda mailfile there, containing the messages that cron emits when it runs the dump. But this is not what amanda sends. Do I need an alias or .forward file someplace? So, where the heck is the mail going? I just changed it to send it to g...@localhost for effect. We'll see if I get a mail tonight. Humm, the manpage doesn't say a thing about quotation marks around that string, so I just took them out, and space separated the two recipients. And we wait -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) An Italian is COMBING his hair in suburban DES MOINES!
quick help needed on changer problem
Hi, today, there have been problems with the tape drive again. Slot 7 could no longer be found in the slot list. I unloaded the module for the SCSI controller and sg and st, then turned off the device and turned it back on and reloaded the modules. Devices are reported as they should. But amtape cannot change slots: prometheus:/etc/cron.daily# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ICP Model: Host Drive #00 Rev: Type: Direct-AccessANSI SCSI revision: 02 Host: scsi4 Channel: 00 Id: 00 Lun: 00 Vendor: EXABYTE Model: VXA 1x10 1U Rev: A102 Type: Medium Changer ANSI SCSI revision: 04 Host: scsi4 Channel: 00 Id: 01 Lun: 00 Vendor: EXABYTE Model: VXA-2Rev: 100E Type: Sequential-AccessANSI SCSI revision: 02 prometheus:/etc/cron.daily# su - backup [EMAIL PROTECTED]:~$ /usr/sbin/amtape condor slot 7 amtape: could not load slot /usr/lib/amanda/chg-zd-mtx:: line 605: [: 6:VolumeTag=: integer expression expected [EMAIL PROTECTED]:~$ /usr/sbin/amtape condor slot 1 amtape: could not load slot /usr/lib/amanda/chg-zd-mtx:: line 605: [: 6:VolumeTag=: integer expression expected [EMAIL PROTECTED]:~$ /usr/sbin/amtape condor slot next amtape: could not load slot /usr/lib/amanda/chg-zd-mtx:: line 605: [: 6:VolumeTag=: integer expression expected Last time I turned the tape off and back on, it helped. Is the above something that might be recovered from by restarting the server, or does it mean that the tape changer is now completely broken? The counting of SCSI devices seems to increase each time I unload and reload the modules, so it's now scsi4 and was scsi3 before. Is that normal? GH
Re: quick help needed on changer problem
listrcv wrote: [EMAIL PROTECTED]:~$ /usr/sbin/amtape condor slot 7 amtape: could not load slot /usr/lib/amanda/chg-zd-mtx:: line 605: [: 6:VolumeTag=: integer expression expected Could you do a `mtx status' and send us the output? Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: quick help needed on changer problem
On Tue, May 16, 2006 at 12:09:29PM +0200, listrcv wrote: ... The counting of SCSI devices seems to increase each time I unload and reload the modules, so it's now scsi4 and was scsi3 before. Is that normal? I'm not familiar enough with Linux to know the correct commands. But in some other OSs devices can be looked for as look for new, or start over again and look for everything. If your system isn't doing a startoveragain, then some small change to your tape could cause it to appear as a new device and get a different name. It has been a while, but ISTR that Fedora has a way of assigning a UUID (Unique U??? ID) to devices, at least to USB devices and I think SCSI as well. Once assigned a table could be constructed of the UUID's and device names that you choose. Then whenever the UUID was detected, regardless of the /dev device automatically assigned, the names you chose were also created. When I used it, it was for several USB external disks that moved around. But whenever any of them were connected, I wanted it mounted in the same place. If your moving scsi problem persists, you might look into the UUID. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: quick help needed on changer problem
Alexander Jolk wrote: listrcv wrote: [EMAIL PROTECTED]:~$ /usr/sbin/amtape condor slot 7 amtape: could not load slot /usr/lib/amanda/chg-zd-mtx:: line 605: [: 6:VolumeTag=: integer expression expected Could you do a `mtx status' and send us the output? Ah, mtx was the program whose name I couldn't remember! prometheus:/home/hwilmer# mtx -f /dev/sg1 status Storage Changer /dev/sg1:1 Drives, 10 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 7 Loaded):VolumeTag = Storage Element 1:Full :VolumeTag= Storage Element 2:Full :VolumeTag= Storage Element 3:Full :VolumeTag= Storage Element 4:Full :VolumeTag= Storage Element 5:Full :VolumeTag= Storage Element 6:Full :VolumeTag= Storage Element 7:Empty:VolumeTag= Storage Element 8:Full :VolumeTag= Storage Element 9:Full :VolumeTag= Storage Element 10:Full :VolumeTag= prometheus:/home/hwilmer# Slot 7 can actually be empty because the tape is in the drive. I made the changer load the tape from slot 7 into the drive via the control panel on the device. Then I started amflush, and to my surprise, it unloaded a tape and loaded one, and it's now writing to the tape. There's a barcode reader or so in the device, but I don't use it. I think the VolumeTag would say what the bar code is if it were used. I'm still waiting for the vendors support to call back to get the device fixed. They already managed to piss me off. Avoid buying exabyte or other stuff from Fujitsu/Siemens. The laptops they make are slow, the tape changer fails after 2 years, and their support sucks. GH
Re: quick help needed on changer problem
Jon LaBadie wrote: On Tue, May 16, 2006 at 12:09:29PM +0200, listrcv wrote: The counting of SCSI devices seems to increase each time I unload and reload the modules, so it's now scsi4 and was scsi3 before. Is that normal? I'm not familiar enough with Linux to know the correct commands. But in some other OSs devices can be looked for as look for new, or start over again and look for everything. There's some way to make the OS looking for SCSI devices like 'cat scsi-add-single-device ... /proc/scsi/scsi' or so. But I didn't want to use that. If your system isn't doing a startoveragain, then some small change to your tape could cause it to appear as a new device and get a different name. As far as I get it, the available SCSI hosts are numbered starting by 0. In case there are several SCSI hosts (like several SCSI controllers or multi-channel controllers or SATA devices that are considered as SCSI besides real SCSI), each host gets another number, counting upwards from 0. Since only the modules were unloaded and reloaded and the physical hosts not changed, I would expect it to get the same number it had before. The total number of hosts was in no way increased. It looks pretty weird in the syslog: May 16 11:52:58 prometheus kernel: st: Unloaded. May 16 11:54:56 prometheus kernel: PCI: Enabling device :02:02.0 (0016 - 0017) May 16 11:54:56 prometheus kernel: scsi3 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 1.3.11 May 16 11:54:56 prometheus kernel: Adaptec 29320A Ultra320 SCSI adapter May 16 11:54:56 prometheus kernel: aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs May 16 11:54:56 prometheus kernel: May 16 11:56:46 prometheus kernel: (scsi3:A:0): 80.000MB/s transfers (40.000MHz, 16bit) May 16 11:56:46 prometheus kernel: (scsi3:A:1): 80.000MB/s transfers (40.000MHz, 16bit) May 16 11:56:49 prometheus kernel: Vendor: EXABYTE Model: VXA 1x10 1U Rev: A102 May 16 11:56:49 prometheus kernel: Type: Medium Changer ANSI SCSI revision: 04 May 16 11:56:49 prometheus kernel: Vendor: EXABYTE Model: VXA-2 Rev: 100E May 16 11:56:49 prometheus kernel: Type: Sequential-Access ANSI SCSI revision: 02 May 16 11:57:49 prometheus kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 May 16 11:57:49 prometheus kernel: Attached scsi generic sg1 at scsi3, channel 0, id 0, lun 0, type 8 May 16 11:57:49 prometheus kernel: Attached scsi generic sg2 at scsi3, channel 0, id 1, lun 0, type 1 May 16 11:57:53 prometheus kernel: st: Version 20040403, fixed bufsize 32768, s/g segs 256 May 16 11:57:53 prometheus kernel: Attached scsi tape st0 at scsi3, channel 0, id 1, lun 0 May 16 11:57:53 prometheus kernel: st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 134217727 May 16 11:59:17 prometheus kernel: st: Unloaded. May 16 11:59:33 prometheus kernel: PCI: Enabling device :02:02.0 (0016 - 0017) May 16 11:59:33 prometheus kernel: scsi4 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 1.3.11 May 16 11:59:33 prometheus kernel: Adaptec 29320A Ultra320 SCSI adapter May 16 11:59:33 prometheus kernel: aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs May 16 11:59:33 prometheus kernel: May 16 11:59:48 prometheus kernel: (scsi4:A:0): 80.000MB/s transfers (40.000MHz, 16bit) May 16 11:59:49 prometheus kernel: (scsi4:A:1): 80.000MB/s transfers (40.000MHz, 16bit) May 16 11:59:52 prometheus kernel: Vendor: EXABYTE Model: VXA 1x10 1U Rev: A102 May 16 11:59:52 prometheus kernel: Type: Medium Changer ANSI SCSI revision: 04 May 16 11:59:52 prometheus kernel: Vendor: EXABYTE Model: VXA-2 Rev: 100E May 16 11:59:52 prometheus kernel: Type: Sequential-Access ANSI SCSI revision: 02 May 16 12:00:15 prometheus kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 May 16 12:00:15 prometheus kernel: Attached scsi generic sg1 at scsi4, channel 0, id 0, lun 0, type 8 May 16 12:00:15 prometheus kernel: Attached scsi generic sg2 at scsi4, channel 0, id 1, lun 0, type 1 At some time, reloading the module will fail because some maximum number of SCSI hosts will be reached (32?), and I would be forced to reboot. That's not good ... Is there some way to renumber the scsi hosts or to reuse them? Then whenever the UUID was detected, regardless of the /dev device automatically assigned, the names you chose were also created. Fortunately, devices are assigned as they should :) Where would I find UIDs on Debian amd64? Hm, maybe I should better post this to the debian-amd64 list? GH
Re: Changer problem
Hello Giovanni You were right - it was a permissions issue on the changer suite of files. Once I corrected them, amanda is functional once again. Your help is much appreciated, Samuel - Original Message - From: Montagni, Giovanni [EMAIL PROTECTED] Try to check permission on changer file (it's owned by amanda?). Then, run amcheck to see if there's a configuration problem. Giovanni -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Samuel Chetty Inviato: mercoledì 9 novembre 2005 15.56 A: amanda-users@amanda.org Oggetto: Changer problem Hello I am experiencing a changer issue, when attempting to manipulate the tape changer (Overland Powerloader); Examples; %amtape my-conf-name eject amtape: slot none not ejected: cannot determine first slot %amtape my-conf-name reset amtape: could not reset changer: cannot determine first slot Can anyone help with a resolution please? Thank you. -- Samuel Chetty
Changer problem
Hello I am experiencing a changer issue, when attempting to manipulate the tape changer (Overland Powerloader); Examples; %amtape my-conf-name eject amtape: slot none not ejected: cannot determine first slot %amtape my-conf-name reset amtape: could not reset changer: cannot determine first slot Can anyone help with a resolution please? Thank you. -- Samuel Chetty [EMAIL PROTECTED]
Re: Changer problem
On Wed, Nov 09, 2005 at 04:55:42PM +0200, Samuel Chetty wrote: Hello I am experiencing a changer issue, when attempting to manipulate the tape changer (Overland Powerloader); Examples; %amtape my-conf-name eject amtape: slot none not ejected: cannot determine first slot %amtape my-conf-name reset amtape: could not reset changer: cannot determine first slot Can anyone help with a resolution please? When making a request like this it helps to tell some of the config details. While the hardware you are using is important, I'm more interested in the software. What OS, what amanda version, what changer script, ... Not armed with that info I looked throught the source for not ejected. Appeared several times. Then I looked for cannot determine first slot and found it only in chg-zd-mtx. So after that I checked the location of the message. It is part of an 'if' statement, if [ $firstslot -lt 0 ] That suggests to me that you did not read through the comments at the start of chg-zd-mtx and set up the changer configuration parameters properly. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
R: Changer problem
Try to check permission on changer file (it's owned by amanda?). Then, run amcheck to see if there's a configuration problem. Giovanni -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Samuel Chetty Inviato: mercoledì 9 novembre 2005 15.56 A: amanda-users@amanda.org Oggetto: Changer problem Hello I am experiencing a changer issue, when attempting to manipulate the tape changer (Overland Powerloader); Examples; %amtape my-conf-name eject amtape: slot none not ejected: cannot determine first slot %amtape my-conf-name reset amtape: could not reset changer: cannot determine first slot Can anyone help with a resolution please? Thank you. -- Samuel Chetty [EMAIL PROTECTED] -- Il contenuto della presente comunicazione è riservato e destinato esclusivamente ai destinatari indicati. Nel caso in cui sia ricevuto da persona diversa dal destinatario sono proibite la diffusione, la distribuzione e la copia. Nel caso riceveste la presente per errore, Vi preghiamo di informarci e di distruggerlo e/o cancellarlo dal Vostro computer, senza utilizzare i dati contenuti. La presente comunicazione (comprensiva dei documenti allegati) non avrà valore di proposta contrattuale e/o accettazione di proposte provenienti dal destinatario, nè rinuncia o riconoscimento di diritti, debiti e/o crediti, nè sarà impegnativa, qualora non sia sottoscritto successivo accordo da chi può validamente obbligarci. Non deriverà alcuna responsabilità precontrattuale a ns. carico, se la presente non sia seguita da contratto sottoscritto dalle parti. -- The contents of the present communication is strictly confidential and reserved solely to the referred addressees. In the event was received by person different from the addressee, it is forbidden the diffusion, distribution and copy. In the event you have received it mistakenly we ask you to inform us and to destroy and/or to delete it by your computer, without using the data herein contained. The present message (eventual annexes inclusive) shall not be considered any contractual proposal and/or acceptance of offer coming from the addressee, nor waiver neither recognizance of rights, debts and/or credits, and it shall not be binding, when it is not executed a subsequent agreement by person who could lawfully represent us. No pre-contractual liability shall derive to us, when the present communication is not followed by any binding agreement between the parties.
tape changer problem
hello again. i have amanda server 2.4.4 installed on sparc solaris 8 with one hp dds3 tape drive. i got error yestarday after nightly backup that amanda cannot dump data to tape caused by following debug information: changer.debug MT - /usr/local/sbin/ammt -f DD - /usr/local/sbin/amdd Args - -info - rewind /dev/rmt/0bn - status /dev/rmt/0bn /dev/rmt/0bn status: ONLINE er == 0x fileno == 0 blkno == 0 - loaded /dev/rmt/0bn status: ONLINE er == 0x fileno == 0 blkno == 0 Exit - 99 1 tape rewinded notrmaly, but 'exit 99 1' looks like that last slot used by chg-manual in previosly backup, and slot not rotated to first again. amlabel.debug contain next strings: changer: got exit: 1 str: /usr/local/libexec/chg-manual: test: argument expected amlabel: could not load slot current: test: argument expected amlabel: pid 10575 finish time Thu Oct 2 12:58:09 [EMAIL PROTECTED] in chg-manual script last available slot is 99. i may to increase this variable, and think this will be enough, but i not sure that right way. any ideas? vlad.
Re: Fwd: tape changer problem
On Thursday 07 March 2002 09:18 am, Zhen Liu wrote: Zhen Liu Via Webmail [EMAIL PROTECTED] This is a repost. Did you not receive my reply from yesterday? That reply should have contained something helpfull... -- Forwarded message --- From: Zhen Liu [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Mon, 04 Mar 2002 12:03:21 -0500 Hi, I am working on the amanda backup project now, and I am a newbie for both amanda and linux... right now, I have some problem with our tape changer...SOS!!! HELP!!! The OS I am working on is Linux RH7.1, the tape changer we have is Adic Fastor, Quantum 7000 tape drive. I guess that something must be wrong with my configuration...when i run amcheck i get amcheck-server: could not get changer info: open: /dev/sg0: success -relevant part from /etc/amanda/daily/amanda.conf runtapes 2 tpchanger chg-scsi tapedev 0 changerfile etc/amanda/DailySet1/changer.conf changerdev dev/sg0 - /etc/amanda/DailySet1/changer.conf- number_configs 1 # eject 1 sleep60 cleanmax 1000 changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum 0 dev /dev/nst0 startuse 0 enduse 6 statfile /etc/amanda/DailySet1/st0-slot cleancart-1 cleanfile/etc/amanda/DailySet1/st0-clean usagecount /etc/amanda/DailySet1/st0-totaltime So, I am totally lost...Help? Thanks... Zhen Liu Via Webmail [EMAIL PROTECTED] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 98.6+% setiathome rank, not too shabby for a hillbilly
Re: amtape and tape changer problem
Hi, Thanks for your prompt response...below are the debug of output (/tmp/amanda)...pls check them...I really appreciate your help!!! [root@apple amanda]# more amtape.20020314082946.debug amtape: debug 1 pid 20641 ruid 33 euid 33 start time Thu Mar 14 08:29:46 2002 changer: got exit: 0 str: 1 7 1 0 changer: got exit: 0 str: 1 /dev/nst0 changer: got exit: 2 str: DeviceCapabilitiesPage == NULL could not load slot DeviceCapabilitiesPage: == NULL amtape: pid 20641 finish time Thu Mar 14 08:31:24 2002 [root@apple amanda]# more chg-scsi.20020314083102.debug chg-scsi: debug 1 pid 20651 ruid 33 euid 33 start time Thu Mar 14 08:31:02 2002 ARG [0] : /usr/lib/amanda/chg-scsi ARG [1] : -slot ARG [2] : next Number of configurations: 1 Tapes need eject: Yes barcode reader : No Tapes need sleep: 70 seconds Cleancycles : 20 Changerdevice : /dev/sgb Tapeconfig Nr: 0 Drivenumber : 0 Startslot : 0 Endslot : 6 Cleanslot : -1 Devicename: /dev/nst0 changerident : none SCSITapedev : none tapeident : none statfile : none Slotfile : /etc/amanda/DailySet1/tape5-slot Cleanfile : /etc/amanda/DailySet1/tape0-clean Usagecount: /etc/amanda/DailySet1/totaltime # START OpenDevice OpenDevice : /dev/sgb SCSI_OpenDevice : use SG interface SCSI_OpenDevice : current timeout 6000 SCSI_OpenDevice : timeout set to 6 # START SCSI_Inquiry SCSI_Inquiry start length = 56: # START DecodeSCSI SCSI_ExecuteCommand : INQUIRY 12 00 00 00 38 00 # STOP DecodeSCSI 08 80 02 02 33 00 00 00 41 44 49 43 20 20 20 203...ADIC 46 61 73 74 53 74 6F 72 20 44 4C 54 20 20 20 20FastStor.DLT 30 31 31 38 00 00 00 00 00 00 00 00 00 00 00 000118 00 00 00 00 00 00 00 00 SCSI_Inquiry : end 0 # START PrintInquiry qualifier 0 type8 data_format 2 ansi_version2 ecma_version0 iso_version 0 type_modifier 0 removable 1 vendor_info ADIC prod_ident FastStor DLT prod_version0118 vendor_specific using ident = generic, type = Generic driver tape/robot [generic] # START OpenDevice OpenDevice : /dev/nst0 SCSI_OpenDevice : checking if /dev/nst0 is a sg device No link /dev/nst0 using ident = generic, type = Generic driver tape/robot [generic] need_eject set to 2 ## START get_drive_count get_drive_count : fd 3 # START GenericElementStatus # START SCSI_ModeSense SCSI_ModeSense start length = 255: # START DecodeSCSI SCSI_ExecuteCommand : MODE SENSE 1A 08 3F 00 FF 00 # STOP DecodeSCSI [root@apple amanda]# clear [root@apple amanda]# more chg-scsi.20020314083102.debug chg-scsi: debug 1 pid 20651 ruid 33 euid 33 start time Thu Mar 14 08:31:02 2002 ARG [0] : /usr/lib/amanda/chg-scsi ARG [1] : -slot ARG [2] : next Number of configurations: 1 Tapes need eject: Yes barcode reader : No Tapes need sleep: 70 seconds Cleancycles : 20 Changerdevice : /dev/sgb Tapeconfig Nr: 0 Drivenumber : 0 Startslot : 0 Endslot : 6 Cleanslot : -1 Devicename: /dev/nst0 changerident : none SCSITapedev : none tapeident : none statfile : none Slotfile : /etc/amanda/DailySet1/tape5-slot Cleanfile : /etc/amanda/DailySet1/tape0-clean Usagecount: /etc/amanda/DailySet1/totaltime # START OpenDevice OpenDevice : /dev/sgb SCSI_OpenDevice : use SG interface SCSI_OpenDevice : current timeout 6000 SCSI_OpenDevice : timeout set to 6 # START SCSI_Inquiry SCSI_Inquiry start length = 56: # START DecodeSCSI SCSI_ExecuteCommand : INQUIRY 12 00 00 00 38 00 # STOP DecodeSCSI 08 80 02 02 33 00 00 00 41 44 49 43 20 20 20 203...ADIC 46 61 73 74 53 74 6F 72 20 44 4C 54 20 20 20 20FastStor.DLT 30 31 31 38 00 00 00 00 00 00 00 00 00 00 00 000118 00 00 00 00 00 00 00 00 SCSI_Inquiry : end 0 # START PrintInquiry qualifier 0 type8 data_format 2 ansi_version2 ecma_version0 iso_version 0 type_modifier 0 removable 1 vendor_info ADIC prod_ident FastStor DLT prod_version0118 vendor_specific using ident = generic, type = Generic driver tape/robot [generic] # START OpenDevice OpenDevice : /dev/nst0 SCSI_OpenDevice : checking if /dev/nst0 is a sg device No link /dev/nst0 using ident = generic, type = Generic driver tape/robot [generic] need_eject set to 2 ## START get_drive_count get_drive_count : fd 3 # START GenericElementStatus # START SCSI_ModeSense SCSI_ModeSense start length = 255: # START DecodeSCSI SCSI_ExecuteCommand : MODE SENSE 1A 08 3F 00 FF 00 # STOP DecodeSCSI SCSI_ModeSense end: 0 # START DecodeModeSense 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e... 1D 12 00 56 00 01 00 01 00 07 00 00 00 00 00 52...V...R 00 01 00 00 1E 02 00 00 1F 0E 0A 00 0A 0B 00 03 00 00 00 00 00 00 00 00 00 2C 43 6F 70 79 72 69..Copyri 67 68 74
Re: amtape and tape changer problem
Hi, On Thu, Mar 14, 2002 at 04:51:10PM -0500, Zhen Liu wrote: [...] # START DecodeModeSense 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e... OK, the problem seems to be here, ADIC returns the results with an different offset than others, to solve this pleas add the following to you chg-scsi.conf and retry it: changerident FastStor_DLT If this helps i will extend chg-scsi to run without this value. Thomas -- --- | Thomas Hepper[EMAIL PROTECTED] | | ( If the above address fail try ) | | ( [EMAIL PROTECTED])| ---
amtape and tape changer problem
Hi, Thank you very much for your suggestion. Meanwhile, I got another problem...when I enter the command amtape daily show I got the following message: scanning all 7 slots in tape-changer rack: slot1: date X Label DailySet11 amtape: could not load slot DeviceCapabilitiesPage: == Null. I am wondering something is wrong about my changer device...but I am not sure what is exactly wrong with it. So, any information or references? pls help!!! Zhen Liu --- It means that it is a unused tape ...if it had been previously used (meaning tape is referred to in the tapelist file) then there will be a reference to the tape. Look in your tapelist file and see if there is any reference to DailySet16 Don Zhen Liu wrote: Hi, I am working on amanda with the Adic Fastor autoloader...Dlt7000... on RH linux 7.1 os... When I run amcheck i got the following message: amcheck-server: slot0: date X label DailySet16 (first labelstr match) So, anyone knows anything wrong with this? why the date shows X instead of the actual date? pls help!!! Thanks, Zhen Liu Via Webmail [EMAIL PROTECTED] Zhen Liu Via Webmail [EMAIL PROTECTED]
Re: amtape and tape changer problem
Hi, On Thu, Mar 14, 2002 at 09:00:06AM -0500, Zhen Liu wrote: Hi, Thank you very much for your suggestion. Meanwhile, I got another problem...when I enter the command amtape daily show I got the following message: scanning all 7 slots in tape-changer rack: slot1: date X Label DailySet11 amtape: could not load slot DeviceCapabilitiesPage: == Null. Hmm, that is an indicator that the device for the robot is wrong. Can you send the debug output (/tmp/amanda) Thomas -- --- | Thomas Hepper[EMAIL PROTECTED] | | ( If the above address fail try ) | | ( [EMAIL PROTECTED])| ---
Re: amtape and tape changer problem
Hi, Thanks for your prompt response...below are the debug of output (/tmp/amanda)...pls check them...I really appreciate your help!!! [root@apple amanda]# more amtape.20020314082946.debug amtape: debug 1 pid 20641 ruid 33 euid 33 start time Thu Mar 14 08:29:46 2002 changer: got exit: 0 str: 1 7 1 0 changer: got exit: 0 str: 1 /dev/nst0 changer: got exit: 2 str: DeviceCapabilitiesPage == NULL could not load slot DeviceCapabilitiesPage: == NULL amtape: pid 20641 finish time Thu Mar 14 08:31:24 2002 [root@apple amanda]# more chg-scsi.20020314083102.debug chg-scsi: debug 1 pid 20651 ruid 33 euid 33 start time Thu Mar 14 08:31:02 2002 ARG [0] : /usr/lib/amanda/chg-scsi ARG [1] : -slot ARG [2] : next Number of configurations: 1 Tapes need eject: Yes barcode reader : No Tapes need sleep: 70 seconds Cleancycles : 20 Changerdevice : /dev/sgb Tapeconfig Nr: 0 Drivenumber : 0 Startslot : 0 Endslot : 6 Cleanslot : -1 Devicename: /dev/nst0 changerident : none SCSITapedev : none tapeident : none statfile : none Slotfile : /etc/amanda/DailySet1/tape5-slot Cleanfile : /etc/amanda/DailySet1/tape0-clean Usagecount: /etc/amanda/DailySet1/totaltime # START OpenDevice OpenDevice : /dev/sgb SCSI_OpenDevice : use SG interface SCSI_OpenDevice : current timeout 6000 SCSI_OpenDevice : timeout set to 6 # START SCSI_Inquiry SCSI_Inquiry start length = 56: # START DecodeSCSI SCSI_ExecuteCommand : INQUIRY 12 00 00 00 38 00 # STOP DecodeSCSI 08 80 02 02 33 00 00 00 41 44 49 43 20 20 20 203...ADIC 46 61 73 74 53 74 6F 72 20 44 4C 54 20 20 20 20FastStor.DLT 30 31 31 38 00 00 00 00 00 00 00 00 00 00 00 000118 00 00 00 00 00 00 00 00 SCSI_Inquiry : end 0 # START PrintInquiry qualifier 0 type8 data_format 2 ansi_version2 ecma_version0 iso_version 0 type_modifier 0 removable 1 vendor_info ADIC prod_ident FastStor DLT prod_version0118 vendor_specific using ident = generic, type = Generic driver tape/robot [generic] # START OpenDevice OpenDevice : /dev/nst0 SCSI_OpenDevice : checking if /dev/nst0 is a sg device No link /dev/nst0 using ident = generic, type = Generic driver tape/robot [generic] need_eject set to 2 ## START get_drive_count get_drive_count : fd 3 # START GenericElementStatus # START SCSI_ModeSense SCSI_ModeSense start length = 255: # START DecodeSCSI SCSI_ExecuteCommand : MODE SENSE 1A 08 3F 00 FF 00 # STOP DecodeSCSI [root@apple amanda]# clear [root@apple amanda]# more chg-scsi.20020314083102.debug chg-scsi: debug 1 pid 20651 ruid 33 euid 33 start time Thu Mar 14 08:31:02 2002 ARG [0] : /usr/lib/amanda/chg-scsi ARG [1] : -slot ARG [2] : next Number of configurations: 1 Tapes need eject: Yes barcode reader : No Tapes need sleep: 70 seconds Cleancycles : 20 Changerdevice : /dev/sgb Tapeconfig Nr: 0 Drivenumber : 0 Startslot : 0 Endslot : 6 Cleanslot : -1 Devicename: /dev/nst0 changerident : none SCSITapedev : none tapeident : none statfile : none Slotfile : /etc/amanda/DailySet1/tape5-slot Cleanfile : /etc/amanda/DailySet1/tape0-clean Usagecount: /etc/amanda/DailySet1/totaltime # START OpenDevice OpenDevice : /dev/sgb SCSI_OpenDevice : use SG interface SCSI_OpenDevice : current timeout 6000 SCSI_OpenDevice : timeout set to 6 # START SCSI_Inquiry SCSI_Inquiry start length = 56: # START DecodeSCSI SCSI_ExecuteCommand : INQUIRY 12 00 00 00 38 00 # STOP DecodeSCSI 08 80 02 02 33 00 00 00 41 44 49 43 20 20 20 203...ADIC 46 61 73 74 53 74 6F 72 20 44 4C 54 20 20 20 20FastStor.DLT 30 31 31 38 00 00 00 00 00 00 00 00 00 00 00 000118 00 00 00 00 00 00 00 00 SCSI_Inquiry : end 0 # START PrintInquiry qualifier 0 type8 data_format 2 ansi_version2 ecma_version0 iso_version 0 type_modifier 0 removable 1 vendor_info ADIC prod_ident FastStor DLT prod_version0118 vendor_specific using ident = generic, type = Generic driver tape/robot [generic] # START OpenDevice OpenDevice : /dev/nst0 SCSI_OpenDevice : checking if /dev/nst0 is a sg device No link /dev/nst0 using ident = generic, type = Generic driver tape/robot [generic] need_eject set to 2 ## START get_drive_count get_drive_count : fd 3 # START GenericElementStatus # START SCSI_ModeSense SCSI_ModeSense start length = 255: # START DecodeSCSI SCSI_ExecuteCommand : MODE SENSE 1A 08 3F 00 FF 00 # STOP DecodeSCSI SCSI_ModeSense end: 0 # START DecodeModeSense 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e... 1D 12 00 56 00 01 00 01 00 07 00 00 00 00 00 52...V...R 00 01 00 00 1E 02 00 00 1F 0E 0A 00 0A 0B 00 03 00 00 00 00 00 00 00 00 00 2C 43 6F 70 79 72 69..Copyri 67 68 74
Fwd: tape changer problem
Zhen Liu Via Webmail [EMAIL PROTECTED] -- Forwarded message --- From: Zhen Liu [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Mon, 04 Mar 2002 12:03:21 -0500 Hi, I am working on the amanda backup project now, and I am a newbie for both amanda and linux... right now, I have some problem with our tape changer...SOS!!! HELP!!! The OS I am working on is Linux RH7.1, the tape changer we have is Adic Fastor, Quantum 7000 tape drive. I guess that something must be wrong with my configuration...when i run amcheck i get amcheck-server: could not get changer info: open: /dev/sg0: success -relevant part from /etc/amanda/daily/amanda.conf runtapes 2 tpchanger chg-scsi tapedev 0 changerfile etc/amanda/DailySet1/changer.conf changerdev dev/sg0 - /etc/amanda/DailySet1/changer.conf- number_configs 1 # eject 1 sleep60 cleanmax 1000 changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum 0 dev /dev/nst0 startuse 0 enduse 6 statfile /etc/amanda/DailySet1/st0-slot cleancart-1 cleanfile/etc/amanda/DailySet1/st0-clean usagecount /etc/amanda/DailySet1/st0-totaltime So, I am totally lost...Help? Thanks... Zhen Liu Via Webmail [EMAIL PROTECTED]
Re: Fwd: tape changer problem
On Thursday 07 March 2002 09:18 am, Zhen Liu wrote: Zhen Liu Via Webmail [EMAIL PROTECTED] This is a repost. Did you not receive my reply from yesterday? That reply should have contained something helpfull... -- Forwarded message --- From: Zhen Liu [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Mon, 04 Mar 2002 12:03:21 -0500 Hi, I am working on the amanda backup project now, and I am a newbie for both amanda and linux... right now, I have some problem with our tape changer...SOS!!! HELP!!! The OS I am working on is Linux RH7.1, the tape changer we have is Adic Fastor, Quantum 7000 tape drive. I guess that something must be wrong with my configuration...when i run amcheck i get amcheck-server: could not get changer info: open: /dev/sg0: success -relevant part from /etc/amanda/daily/amanda.conf runtapes 2 tpchanger chg-scsi tapedev 0 changerfile etc/amanda/DailySet1/changer.conf changerdev dev/sg0 - /etc/amanda/DailySet1/changer.conf- number_configs 1 # eject 1 sleep60 cleanmax 1000 changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum 0 dev /dev/nst0 startuse 0 enduse 6 statfile /etc/amanda/DailySet1/st0-slot cleancart-1 cleanfile/etc/amanda/DailySet1/st0-clean usagecount /etc/amanda/DailySet1/st0-totaltime So, I am totally lost...Help? Thanks... Zhen Liu Via Webmail [EMAIL PROTECTED] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 98.6+% setiathome rank, not too shabby for a hillbilly
Re: Fwd: tape changer problem
Hi, i bet sg0 is not your correct changer-device. What do you get if you type: cat /proc/scsi/scsi this shows you the devices known to your linux-system. In this list locate your changer. If it's the firste device, /dev/sg0 is ok, if its the second, use /dev/sg1 .. Hope it helps Christoph Zhen Liu schrieb: Zhen Liu Via Webmail [EMAIL PROTECTED] -- Forwarded message --- From: Zhen Liu [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Mon, 04 Mar 2002 12:03:21 -0500 Hi, I am working on the amanda backup project now, and I am a newbie for both amanda and linux... right now, I have some problem with our tape changer...SOS!!! HELP!!! The OS I am working on is Linux RH7.1, the tape changer we have is Adic Fastor, Quantum 7000 tape drive. I guess that something must be wrong with my configuration...when i run amcheck i get amcheck-server: could not get changer info: open: /dev/sg0: success -relevant part from /etc/amanda/daily/amanda.conf runtapes 2 tpchanger chg-scsi tapedev 0 changerfile etc/amanda/DailySet1/changer.conf changerdev dev/sg0 - /etc/amanda/DailySet1/changer.conf- number_configs 1 # eject 1 sleep60 cleanmax 1000 changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum 0 dev /dev/nst0 startuse 0 enduse 6 statfile /etc/amanda/DailySet1/st0-slot cleancart-1 cleanfile/etc/amanda/DailySet1/st0-clean usagecount /etc/amanda/DailySet1/st0-totaltime So, I am totally lost...Help? Thanks... Zhen Liu Via Webmail [EMAIL PROTECTED]
Fwd: help for tape changer problem
Zhen Liu Via Webmail [EMAIL PROTECTED] -- Forwarded message --- From: Zhen Liu [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Tue, 05 Mar 2002 11:26:40 -0500 Zhen Liu Via Webmail [EMAIL PROTECTED] -- Forwarded message --- From: Zhen Liu [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Mon, 04 Mar 2002 12:03:21 -0500 Hi, I am working on the amanda backup project now, and I am a newbie for both amanda and linux... right now, I have some problem with our tape changer...SOS!!! HELP!!! The OS I am working on is Linux RH7.1, the tape changer we have is Adic Fastor, Quantum 7000 tape drive. I guess that something must be wrong with my configuration...when i run amcheck i get amcheck-server: could not get changer info: open: /dev/sg0: success -relevant part from /etc/amanda/daily/amanda.conf runtapes 2 tpchanger chg-scsi tapedev 0 changerfile etc/amanda/DailySet1/changer.conf changerdev dev/sg0 - /etc/amanda/DailySet1/changer.conf- number_configs 1 # eject 1 sleep60 cleanmax 1000 changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum 0 dev /dev/nst0 startuse 0 enduse 6 statfile /etc/amanda/DailySet1/st0-slot cleancart-1 cleanfile/etc/amanda/DailySet1/st0-clean usagecount /etc/amanda/DailySet1/st0-totaltime So, I am totally lost...Help? Thanks... Zhen Liu Via Webmail [EMAIL PROTECTED]
Re: Fwd: help for tape changer problem
On Wednesday 06 March 2002 09:37 am, Zhen Liu wrote: [snip] From: Zhen Liu [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Mon, 04 Mar 2002 12:03:21 -0500 Hi, I am working on the amanda backup project now, and I am a newbie for both amanda and linux... right now, I have some problem with our tape changer...SOS!!! HELP!!! The OS I am working on is Linux RH7.1, the tape changer we have is Adic Fastor, Quantum 7000 tape drive. I guess that something must be wrong with my configuration...when i run amcheck i get amcheck-server: could not get changer info: open: /dev/sg0: success -relevant part from /etc/amanda/daily/amanda.conf runtapes 2 tpchanger chg-scsi tapedev 0 changerfile etc/amanda/DailySet1/changer.conf changerdev dev/sg0 I don't believe this is the correct device for the changer although it varies from mechanism to mechanism. It also isn't required to define it twice as you have here, and in fact it could confuse things. Some changers address the changer robot at the next device up in the scsi address scheme, and some will address it at Logical Unit 1 at the same bus ID number as the drive is, using lun 0 for the drive. In order to see the rest of such a device that uses lun's other than 0, you will have to re-compile your kernel after turning on the 'SCAN ALL LUNS' option with a make xconfig or other method. This will make the boot a little slower, particularly if the actual device address is 6 as it will scan all luns for all bus addresses, taking about 1 second per lun at 7 luns per address. Because of this, I usually set the hardware address to whatever is the next one above any disk drives, purposely placing the disks first in the find sequence so they don't get re-addressed if the tape drive sneezes wrong. Once that is done and the new kernel installed and the machine rebooted, you may then inspect (less /var/log/dmesg) the boot records to see what actual device has been assigned to the robot when it was found. Insert that line in the changer.conf file, leaving the one in amanda.conf out completely. - /etc/amanda/DailySet1/changer.conf- number_configs 1 # eject 1 sleep60 cleanmax 1000 changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum 0 dev /dev/nst0 startuse 0 enduse 6 statfile /etc/amanda/DailySet1/st0-slot cleancart-1 cleanfile/etc/amanda/DailySet1/st0-clean usagecount /etc/amanda/DailySet1/st0-totaltime So, I am totally lost...Help? Do you keep a cleaning tape in the last numerical slot? If so, reduce the enduse by one, and tell it the 'cleancart' is in that last slot. Amanda will then do it automaticly (or should anyway) when the drive says it needs cleaning. And FWIW, cleaning tapes should not be reused 1000 times as they will have become way too contaminated to be usefull after 5 or 6 passes at best. But, amanda counts the number of times its been used for one cleaning cycle, and that normally is just a small fraction of the tape in the cartridge. Some drives won't even rewind the cleaning tape, forcing a fresh tape when that one is used up. -- Cheers, Gene
help for tape changer problem
Zhen Liu Via Webmail [EMAIL PROTECTED] -- Forwarded message --- From: Zhen Liu [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Mon, 04 Mar 2002 12:03:21 -0500 Hi, I am working on the amanda backup project now, and I am a newbie for both amanda and linux... right now, I have some problem with our tape changer...SOS!!! HELP!!! The OS I am working on is Linux RH7.1, the tape changer we have is Adic Fastor, Quantum 7000 tape drive. I guess that something must be wrong with my configuration...when i run amcheck i get amcheck-server: could not get changer info: open: /dev/sg0: success -relevant part from /etc/amanda/daily/amanda.conf runtapes 2 tpchanger chg-scsi tapedev 0 changerfile etc/amanda/DailySet1/changer.conf changerdev dev/sg0 - /etc/amanda/DailySet1/changer.conf- number_configs 1 # eject 1 sleep60 cleanmax 1000 changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum 0 dev /dev/nst0 startuse 0 enduse 6 statfile /etc/amanda/DailySet1/st0-slot cleancart-1 cleanfile/etc/amanda/DailySet1/st0-clean usagecount /etc/amanda/DailySet1/st0-totaltime So, I am totally lost...Help? Thanks... Zhen Liu Via Webmail [EMAIL PROTECTED]
tape changer problem
Hi, I am working on the amanda backup project now, and I am a newbie for both amanda and linux... right now, I have some problem with our tape changer...SOS!!! HELP!!! The OS I am working on is Linux RH7.1, the tape changer we have is Adic Fastor, Quantum 7000 tape drive. I guess that something must be wrong with my configuration...when i run amcheck i get amcheck-server: could not get changer info: open: /dev/sg0: success -relevant part from /etc/amanda/daily/amanda.conf runtapes 2 tpchanger chg-scsi tapedev 0 changerfile etc/amanda/DailySet1/changer.conf changerdev dev/sg0 - /etc/amanda/DailySet1/changer.conf- number_configs 1 # eject 1 sleep60 cleanmax 1000 changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum 0 dev /dev/nst0 startuse 0 enduse 6 statfile /etc/amanda/DailySet1/st0-slot cleancart-1 cleanfile/etc/amanda/DailySet1/st0-clean usagecount /etc/amanda/DailySet1/st0-totaltime So, I am totally lost...Help? Thanks... Zhen Liu Via Webmail [EMAIL PROTECTED]
Re: changer problem
I was having problems similar to this (though I can't remember the specific error messages). I'm using chg-zd-mtx on Solaris 8 with an Overland LoaderXpress (DLT). What solved the problem for me was making sure that the changer config file has _all_ of the variables specified, even if they seemed to be default values. The chg-zd-mtx script doesn't seem to set default values, and gives weird errors if they're not there. --rowan Lo, Donnie Emeson and the coffee pot sang in unison: I'm having trouble with amanda 2.4.2p2 and a new changer, a Sun L20 with 20 slots and one DLT8000. This changer has a barcode reader, but I'm not using it. (I don't have a label maker and don't really want to bother.) Perhaps this is what's causing my problems... I have chg-zd-mtx working, though I had to make some minor changes. The problem is amlabel and amcheck. Both get similar errors. Amlabel goes ahead and loads the first tape and then gives me: amlabel: could not load slot current: badly formed result from changer: MT=/usr/bin/mt Amcheck is fine except for this error: amcheck-server: could not get changer info: badly formed result from changer: MT=/usr/bin/mt [snip] -- John Rowan Littell Systems Administrator Earlham College Computing Services PGP signature
Re: changer problem
Hello Donnie !!! I have the same hardware (StorEdge L20) I was not able to set amanda with this L20 May i see your configs files (amanda and chg-zd-mtx) thank's in advance !!! P.S. I can try it and see if a have the same problem than you !!! - Original Message - From: Donnie Emeson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 18, 2001 12:16 AM Subject: changer problem I'm having trouble with amanda 2.4.2p2 and a new changer, a Sun L20 with 20 slots and one DLT8000. This changer has a barcode reader, but I'm not using it. (I don't have a label maker and don't really want to bother.) Perhaps this is what's causing my problems... I have chg-zd-mtx working, though I had to make some minor changes. The problem is amlabel and amcheck. Both get similar errors. Amlabel goes ahead and loads the first tape and then gives me: amlabel: could not load slot current: badly formed result from changer: MT=/usr/bin/mt Amcheck is fine except for this error: amcheck-server: could not get changer info: badly formed result from changer: MT=/usr/bin/mt # cat /tmp/amanda/amlabel.20011017213837.debug amlabel: debug 1 pid 27110 ruid 43382 euid 43382 start time Wed Oct 17 21:38:37 2001 changer: got exit: 0 str: MT=/usr/bin/mt could not load slot current: badly formed result from changer: MT=/usr/bin/mt amlabel: pid 27110 finish time Wed Oct 17 21:40:07 2001 # cat /tmp/amanda/amcheck.20011017213225.debug amcheck: debug 1 pid 27006 ruid 43382 euid 0 start time Wed Oct 17 21:32:25 2001 amcheck: dgram_bind: socket bound to 0.0.0.0.711 changer: got exit: 0 str: MT=/usr/bin/mt changer_query: changer return was could not get changer info: badly formed result from changer: MT=/usr/bin/mt amcheck-server: pid 27007 finish time Wed Oct 17 21:32:25 2001 amcheck: pid 27006 finish time Wed Oct 17 21:32:25 2001 --donnie
changer problem
I'm having trouble with amanda 2.4.2p2 and a new changer, a Sun L20 with 20 slots and one DLT8000. This changer has a barcode reader, but I'm not using it. (I don't have a label maker and don't really want to bother.) Perhaps this is what's causing my problems... I have chg-zd-mtx working, though I had to make some minor changes. The problem is amlabel and amcheck. Both get similar errors. Amlabel goes ahead and loads the first tape and then gives me: amlabel: could not load slot current: badly formed result from changer: MT=/usr/bin/mt Amcheck is fine except for this error: amcheck-server: could not get changer info: badly formed result from changer: MT=/usr/bin/mt # cat /tmp/amanda/amlabel.20011017213837.debug amlabel: debug 1 pid 27110 ruid 43382 euid 43382 start time Wed Oct 17 21:38:37 2001 changer: got exit: 0 str: MT=/usr/bin/mt could not load slot current: badly formed result from changer: MT=/usr/bin/mt amlabel: pid 27110 finish time Wed Oct 17 21:40:07 2001 # cat /tmp/amanda/amcheck.20011017213225.debug amcheck: debug 1 pid 27006 ruid 43382 euid 0 start time Wed Oct 17 21:32:25 2001 amcheck: dgram_bind: socket bound to 0.0.0.0.711 changer: got exit: 0 str: MT=/usr/bin/mt changer_query: changer return was could not get changer info: badly formed result from changer: MT=/usr/bin/mt amcheck-server: pid 27007 finish time Wed Oct 17 21:32:25 2001 amcheck: pid 27006 finish time Wed Oct 17 21:32:25 2001 --donnie
Re: small changer problem yet
Hi, On Mon, Aug 27, 2001 at 11:49:51AM -0400, Gene Heskett wrote: I've about got amanda working with a Compaq/Seagate 4586 now, but one thing I need to clarify. When I issue as user amanda, amverify config 2 it should proceed to do a verify run on slot 2's contents, or at least thats how I understand it. What it does, even if slot 2 is loaded with the correct tape, is to give an error from amtape indicating it can't load or read the tape. It then proceeds to look at slot 3, see's a labeled but otherwise blank tape there, then goes back to slot 1, does a full verify on that tape, then reloads slot 2 and does a verify on that tape, which is what it should have done in the first place. Is this a bug, or am I not issueing the correct command syntax? Inquiring minds want to know. if you use chg-scsi it's a bug, and i'm working on a fix Thomas -- --- | Thomas Hepper[EMAIL PROTECTED] | | ( If the above address fail try ) | | ( [EMAIL PROTECTED])| ---
small changer problem yet
I've about got amanda working with a Compaq/Seagate 4586 now, but one thing I need to clarify. When I issue as user amanda, amverify config 2 it should proceed to do a verify run on slot 2's contents, or at least thats how I understand it. What it does, even if slot 2 is loaded with the correct tape, is to give an error from amtape indicating it can't load or read the tape. It then proceeds to look at slot 3, see's a labeled but otherwise blank tape there, then goes back to slot 1, does a full verify on that tape, then reloads slot 2 and does a verify on that tape, which is what it should have done in the first place. Is this a bug, or am I not issueing the correct command syntax? Inquiring minds want to know. Cheers, Gene
Re: HP Surestore changer problem
On Nov 1, 2000, Rob Simmons [EMAIL PROTECTED] wrote:
%cat /dev/nsa0
cat: /dev/nsa0: Input/output error
cat won't always use 32Kb. Use `dd bs=32k if=/dev/nsa0' instead.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
HP Surestore changer problem
I am having a problem with the settings for a HP C1557A Surestore 24x6 tape changer with amanda 2.4.1p1 and FreeBSD 4.1.1-RELEASE. The driver is working properly, but I don't think I have the setting for the drive correct. amcheck gives the following error: %amcheck normal Amanda Tape Server Host Check - /hold/amanda: 53130264 KB disk space available, that's plenty. amcheck-server: could not get changer info: 6 1 The strange thing is that amlabel is able to label the tapes just fine (maybe?). I noticed that when I try to cat the device after labeling it I get this error: %cat /dev/nsa0 cat: /dev/nsa0: Input/output error And this error shows up in /var/log/messages: Nov 1 16:22:05 bofh /kernel: (sa0:sym0:0:5:0): 32768-byte tape record bigger than suplied buffer Nov 1 16:22:05 bofh /kernel: (sa0:sym0:0:5:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. I believe the problem is in the settings for the tape changer itself. Here is the output from mt status: %mt -f /dev/nsa0 status Mode Density Blocksize bpi Compression Current: 0x25:DDS-3 variable 97000disabled -available modes- 0:0x25:DDS-3 variable 97000DCLZ 1:0x25:DDS-3 variable 97000DCLZ 2:0x25:DDS-3 variable 97000DCLZ 3:0x25:DDS-3 variable 97000DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 0 I have tried changing the blocksize to 32768: %mt blocksize 32768 %mt status Mode Density Blocksize bpi Compression Current: 0x25:DDS-3 32768 bytes97000disabled -available modes- 0:0x25:DDS-3 32768 bytes97000DCLZ 1:0x25:DDS-3 32768 bytes97000DCLZ 2:0x25:DDS-3 32768 bytes97000DCLZ 3:0x25:DDS-3 32768 bytes97000DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 0 After the change, the following message shows up in /var/log/messages: Nov 1 16:32:35 bofh /kernel: (sa0:sym0:0:5:0): Invalid request. Fixed block device requests must be a multiple of 32768 bytes -- Robert Simmons Systems Administrator http://www.wlcg.com/
Re: HP Surestore changer problem
I am having a problem with the settings for a HP C1557A Surestore 24x6 tape changer with amanda 2.4.1p1 and FreeBSD 4.1.1-RELEASE. ... Which Amanda tape changer are you trying to use? I noticed that when I try to cat the device after labeling it I get this error: %cat /dev/nsa0 cat: /dev/nsa0: Input/output error You cannot use "cat" to look at tapes. Use "dd" instead, and make sure you position the tape first: % mt -f /dev/nsa0 rewind % dd if=/dev/nsa0 bs=32k Tapes are processed in "raw" mode, which means reads and writes must match the physical record sizes. The "cat" program doesn't know anything about that so uses some default buffer size that is obviously not 32 KBytes, based on the errors you're getting. The "dd" program allows you to set the buffer size. I have tried changing the blocksize to 32768: I would leave it variable. Robert Simmons John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: HP Surestore changer problem
On Wed, 1 Nov 2000, John R. Jackson wrote: I am having a problem with the settings for a HP C1557A Surestore 24x6 tape changer with amanda 2.4.1p1 and FreeBSD 4.1.1-RELEASE. ... Which Amanda tape changer are you trying to use? I'm using chg-chio. I noticed that when I try to cat the device after labeling it I get this error: %cat /dev/nsa0 cat: /dev/nsa0: Input/output error You cannot use "cat" to look at tapes. Use "dd" instead, and make sure you position the tape first: % mt -f /dev/nsa0 rewind % dd if=/dev/nsa0 bs=32k Bingo. Thanks. Tapes are processed in "raw" mode, which means reads and writes must match the physical record sizes. The "cat" program doesn't know anything about that so uses some default buffer size that is obviously not 32 KBytes, based on the errors you're getting. The "dd" program allows you to set the buffer size. I have tried changing the blocksize to 32768: I would leave it variable. Thanks, I set it back to variable. Robert Simmons John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: HP Surestore changer problem
I just figured out the problem. I removed the picker problem from chg-chio, but I didn't remove the STDERR problem. I just removed the STDERR problem, and everything is working fine. -- Robert Simmons Systems Administrator http://www.wlcg.com/ On Wed, 1 Nov 2000, John R. Jackson wrote: I am having a problem with the settings for a HP C1557A Surestore 24x6 tape changer with amanda 2.4.1p1 and FreeBSD 4.1.1-RELEASE. ... Which Amanda tape changer are you trying to use? I noticed that when I try to cat the device after labeling it I get this error: %cat /dev/nsa0 cat: /dev/nsa0: Input/output error You cannot use "cat" to look at tapes. Use "dd" instead, and make sure you position the tape first: % mt -f /dev/nsa0 rewind % dd if=/dev/nsa0 bs=32k Tapes are processed in "raw" mode, which means reads and writes must match the physical record sizes. The "cat" program doesn't know anything about that so uses some default buffer size that is obviously not 32 KBytes, based on the errors you're getting. The "dd" program allows you to set the buffer size. I have tried changing the blocksize to 32768: I would leave it variable. Robert Simmons John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
