Re: broken pipe
Am Donnerstag, 15. Februar 2001 08:51 schrieben Sie:
Hi Alexandre!
Also the backup is finnished correctly?
I'd guess so, but you didn't post the part of the report that says
which dumps made to which tape, so I can't tell for sure.
OK, i send you the complete mail from amanda and hope that it helps:
Begin complete mail fom Amanda
These dumps were to tapes Daily01, Daily02.
Tonight's dumps should go onto 2 tapes: Daily03, Daily04.
FAILURE AND STRANGE DUMP SUMMARY:
fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
fileserver sdc1 lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:10
Run Time (hrs:min) 3:45
Dump Time (hrs:min)2:41 2:41 0:00
Output Size (meg) 44392.544392.50.0
Original Size (meg) 44392.544392.50.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped4 4 0
Avg Dump Rate (k/s) 4713.1 4713.1--
Tape Time (hrs:min)2:41 2:41 0:00
Tape Size (meg) 44392.644392.60.0
Tape Used (%) 111.0 111.00.0
Filesystems Taped 4 4 0
Avg Tp Write Rate (k/s) 4710.0 4710.0--
FAILED AND STRANGE DUMP DETAILS:
/-- fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
sendbackup: start [fileserver:sdc1 level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
| DUMP: Date of this level 0 dump: Thu Feb 15 04:14:16 2001
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/sdc1 (/test/platte3) to standard output
| DUMP: Label: none
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 13086232 tape blocks.
| DUMP: Volume 1 started at: Thu Feb 15 04:14:58 2001
| DUMP: dumping (Pass III) [directories]
| DUMP: dumping (Pass IV) [regular files]
| DUMP: 10.23% done, finished in 0:43
| DUMP: 21.75% done, finished in 0:35
| DUMP: 33.32% done, finished in 0:30
| DUMP: 44.95% done, finished in 0:24
| DUMP: 57.16% done, finished in 0:18
| DUMP: 68.34% done, finished in 0:13
| DUMP: 80.59% done, finished in 0:08
\
NOTES:
taper: tape Daily01 kb 44245472 fm 4 writing file: No space left on device
taper: retrying fileserver:sdc1.0 on new tape: [writing file: No space left
on device]
taper: tape Daily02 kb 13135584 fm 1 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
fileserver sdb10 1319558413195584 -- 40:525380.8 40:555375.7
fileserver sdc10 1313555213135552 -- 45:114844.5 45:134840.9
fileserver sdd10 92850889285088 -- 30:535009.9 30:555005.7
king hdb10 98416969841696 -- 43:483745.2 43:483744.4
(brought to you by Amanda version 2.4.2-19991216-beta1)
---End of Mail from Amanda
Bye Jeurgen
--
Dies ist eine Microsoft freie Mail!
Re: access as amanda not allowed from amanda@foo.sys.si.tlan] amandahostsauth failed
On Thursday 15 February 2001 09:06, Gerhard den Hollander wrote: You get a message saying Banzai ! Did you install the WWII - japanese slang add-on to Amanda ? [Just kidding] ; Ehm do you have the .amandahosts in user amandas homedir ? or only in roots homedir ? In amandas home dir. root doesn't even have .amandahosts The amanda FAQ (docs/FAQ in the source tree) sez this Q: Why does `amcheck' say `access as username not allowed...' A: There must be something wrong with .amandahosts configuration (or .rhosts, if you have configured --without-amandahosts). That I know. But, the fact is there's nothing wrong with it. I have about two dozen machines setup in exactly the same way that this one is. All of them work... This is because I compiled amanda client and made a tgz package that I install on each machine... And then change the .amandahosts file... Make sure you specify the names exactly as they appear in the error message after the `@' sign in .amandahosts/.rhosts. You'll need a fully-qualified domain name or not, depending on how your client resolves IP addresses to host names. Well I'll double check, but I can be pretty sure that everything is setup exactly like it is on all the other hosts. -- David Klasinc Turbolinux Inc. http://www.turbolinux.com
Re: access as amanda not allowed from amanda@foo.sys.si.tlan] amandahostsauth failed
On Feb 15, 2001, David Klasinc [EMAIL PROTECTED] wrote:
if I do it as user amanda, then it fails. I have users root and amanda in
.amandahosts.
What are the exact contents of .amandahosts on the client?
--
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
tapelist
i thought there was a tipelist file for each configuration file, so amanda could know which tape was on turn. i have 2 configuration files, 1 for weekly days and 1 for wednesday, there is just one tapelist in the first one directory. Can you help me thanks
Re: broken pipe
On Feb 15, 2001, Juergen Knott [EMAIL PROTECTED] wrote:
fileserver sdb10 1319558413195584 -- 40:525380.8 40:555375.7
fileserver sdc10 1313555213135552 -- 45:114844.5 45:134840.9
fileserver sdd10 92850889285088 -- 30:535009.9 30:555005.7
king hdb10 98416969841696 -- 43:483745.2 43:483744.4
See? No failures. You can use amtoc or amadmin info to find out in
which tape the filesystem was stored.
--
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
Re: tapelist
On Feb 15, 2001, Monserrat Seisdedos Nuez [EMAIL PROTECTED] wrote:
i have 2 configuration files, 1 for weekly days and 1 for wednesday, there
is just one tapelist in the first one directory.
This probably means the `tapelist' entry in the second directory's
amanda.conf says it should use the same tapelist file as the other
configuration.
--
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
Re: broken pipe
Am Donnerstag, 15. Februar 2001 09:50 schrieben Sie: See? No failures. You can use amtoc or amadmin info to find out in which tape the filesystem was stored. OK, no failure. Amadmin tell me that the backup is ok. I thank you for your help and Infos. Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: amcheck: access as........
* Jrn Hildebrandt [EMAIL PROTECTED] (Thu, Feb 15, 2001 at 11:44:28AM +0100) Amanda Backup Client Hosts Check ERROR: saturn.systemelektronik.de: [access as amanda not allowed from [EMAIL PROTECTED]] Client check: 1 host checked in 0.019 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1) i am little bit astonished as new linux-user about "access as amanda not allowed." because i'm running this command as root. Yes, but the client tries to run amanda as amanda (check the docs in /usr/share/doc/packages/amanda) BTW suse 7.0 ships with amanda-2.4.1p1-157 you might wanna upgrade to 2.4.2p2. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Bad pattern match on disklist
On Thu, Feb 15, 2001 at 02:54:58AM -0200, Alexandre Oliva wrote: On Feb 15, 2001, Mario Obejas [EMAIL PROTECTED] wrote: amadmin ssm1 info hostx / See `man amdmin'. disk is a regular expression in 2.4.1p1; use `/$'. In 2.4.2, a new pattern matching scheme was introduced. `/' should no longer match other disks in 2.4.2. The new pattern matching scheme is not available in 2.4.2, it is only available in the 2.5.0 branch. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Help please for (very) novice user
Hi! first of all let me explain my position. I have been asked to help sort out some systems by giving a few hours a week. The first problem I have is to fix their backup system, which is 'amanda'. I am familiar with Unix but this is the first time I've come across amanda. I have had a quick look at how amanda works and I've had a look at the log files on the failing system. The first error that appears in the log is this: [label tape1_125 or new tape not found in rack] Now I had a quick try at running the backup script that was in cron (runs as user 'ops') and it gave this error. But I had just inserted blank new tapes! Does it need pre-labelled tapes? (The next thing I'll try is to re-use some of the old tapes). Also I noticed that the "main holding disk" is 100% full. Would this cause this error? Next thing to try is clearing this out. I am not even sure if the software is seeing the tape. In the file amanda.conf(and I'm *assuming* this is the configuration file) there is a line: tapedev "/dev/rmt/0bn" and if I run 'mt -f /dev/rmt/0bn' it says no such device. Maybe I need to reboot and specify -r to rebuild the kernel (this machine is a Sparc running SunOS 5.5.1) I looked in 'dmesg' but I couldn't see a reference to a tape unit. Just before I left I desided to run amcheck, here is what happened: $ amcheck DailySet1 amcheck: could not cd to confdir /usr/local/amanda/etc/amanda/DailySet1: No such file or directory $ ls /usr/local/amanda/etc/amanda amanda amanda.conf tape1tape2 $ amcheck tape1 Amanda Tape Server Host Check - ERROR: holding disk /disk/home3/AMANDA/tape1: statfs: No such file or directory amcheck-server: slot 2: slot is empty amcheck-server: slot 2: slot is empty ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /usr/local/amanda/logs/tape1/laphroaig: does not exist NOTE: info dir /usr/local/amanda/logs/tape1/alcyone: does not exist etc etc Well I know this is all a bit vague but I'd just like to get this going again as it is currently a real mess. Anyway, I'll have a bash at getting things working tonight but if anyone can shed any light, or give me some useful advice, I'd be very grateful. Cheers, Ross -- Ross Macintyre Heriot-Watt University [EMAIL PROTECTED]
Re: tapetype for AIT-2 50Gb native?
hi folks,
thanks for the responses! thanks to Yura Pismerov who responded to
me but appearently did not CC to the list.
after getting these, i went and did what i should have done in the
first place: build and run tape-src/tapetype ;*) here's what
tapetype generated for me (no hardware compression of course):
# tapetype -e 50g -f /dev/rmt/1 -t SDX-500C
wrote 1392640 32Kb blocks in 85 files in 8025 seconds (short write)
wrote 1392640 32Kb blocks in 170 files in 7998 seconds (short write)
define tapetype SDX-500C {
comment "just produced by tapetype program"
length 43520 mbytes
filemark 0 kbytes
speed 5562 kps
}
so i guess that must be 50 x 1000 x 1000 x 1000 bytes on the tape,
and not 50 x 1024 x 1024 x 1024 bytes :*)))
hardware is COMPAQ branded SDX-500C tapedrive in a COMPAQ
StorageWorks SSL2000 series library, attached to a Sun Ultra60
450MHz/512Mb using a SunSwift(tm) PCI Adapter card in the 66MHz
pci slot as the SCSI interface, Solaris 8 is the OS. amanda
version (tapetype cmd) is 2.4.2 release.
now, that "filemark 0 kbytes" kinda worries me ;*) i can find no
reference to tape marks in my Compaq AIT drive manual :*/ would
it be a good idea to arbitrarily put in "filemark 1024 bytes"
or something (should it be a Mb or a Kb)?
OTOH, AIT uses MIC (Memory-In-Cassette) technology, so perhaps
the tapedrive does not even write filemarks!?!? anyone have any
insight here?
sincerely,
chris linn
P.S. please CC to me since i appear to not be subscribed to
amanda-users..
On Tue, Feb 13, 2001 at 03:47:36PM -0500, Joseph Del Corso wrote:
Found myself in the same position yesterday.
Try this:
http://www.amanda.org/fom-serve/cache/1.html
Joe
On Tue, Feb 13, 2001 at 15:55:08 -0500, Yura Pismerov wrote:
define tapetype AIT2 {
comment "AIT-2 in Spectralogics TreeFrog"
length 51000 mbytes
filemark 1541 kbytes
speed 5000 kps
lbl-templ "/usr/local/etc/amanda/labels/Generic.ps"
}
[...]
Yuri Pismerov, TUCOWS.COM INC.
--
Christopher Linn, [EMAIL PROTECTED]| By no means shall either the CEC
Staff System Administrator| or MTU be held in any way liable
Center for Experimental Computation | for any opinions or conjecture I
Michigan Technological University | hold to or imply to hold herein.
Re: amlabel + rack of tapes question
* Joseph Del Corso [EMAIL PROTECTED] (Thu, Feb 15, 2001 at 11:03:16AM -0500) Is it possible to amlabel an entire rack of tapes without doing it manually for each tape? Specifically I have roughly 35 tapes that I'd like to label in some kind of automated fashion all at once. Besides writing my own script (which would take time and more than likely a HECK of a lot of debugging) is there an easier way to do this? How about #!/bin/sh for i in mylabel01 mylabel02 mylabel35 do amlabel myconfig $i amtape slot next done (assuming you have a tapechanger capable of holding 35 tapes ) Gerhard, (@jasongeo.com) == The Acoustic Motorbiker == -- __0 Time has a way of taking time =`\, Loneliness is not only felt be fools (=)/(=) Alone I call to ease the pain
Re: tapetype for AIT-2 50Gb native?
Christopher Linn wrote:
after getting these, i went and did what i should have done in the
first place: build and run tape-src/tapetype ;*) here's what
tapetype generated for me (no hardware compression of course):
Are you really really sure the hardware compression is really off?
# tapetype -e 50g -f /dev/rmt/1 -t SDX-500C
wrote 1392640 32Kb blocks in 85 files in 8025 seconds (short write)
wrote 1392640 32Kb blocks in 170 files in 7998 seconds (short write)
define tapetype SDX-500C {
comment "just produced by tapetype program"
length 43520 mbytes
This is about the amount if hardware compression is ON!
filemark 0 kbytes
speed 5562 kps
}
so i guess that must be 50 x 1000 x 1000 x 1000 bytes on the tape,
and not 50 x 1024 x 1024 x 1024 bytes :*)))
yes, usually vendors use "Marketingbytes", which have 1000 in a kilo.
hardware is COMPAQ branded SDX-500C tapedrive in a COMPAQ
StorageWorks SSL2000 series library, attached to a Sun Ultra60
450MHz/512Mb using a SunSwift(tm) PCI Adapter card in the 66MHz
pci slot as the SCSI interface, Solaris 8 is the OS. amanda
version (tapetype cmd) is 2.4.2 release.
Did you adapt the file /kernel/drv/st.conf to define your tapedevice?
If not, that's probably the reason why you have hardware compression
on.
--
Paul Bijnens, Lant Tel +32 16 40.51.40
Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61
http://www.lant.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***
Re: amlabel + rack of tapes question
Hi Joe,
Writing a script is a lot easier than you might think--I just did it to
label about 90 tapes using a DDS4 autoloader with 8 tape magazine, it
was just a 14 line tcsh script with almost no debugging involved. The
script is very site-specific since it was a one-off type of project, but
I attached it anyway so you can get some ideas. My script labels one
magazine full of tapes, then you have to reload the magazine and run the
script again. It wouldn't be too hard to change the script to use the
correct amanda API like using amtape and getting info from amanda.conf
file, but I haven't got the time or motivation to do it right now.
If you're in the middle of your dump cycle and want to add some tapes
onto the end of the dump cycle, the tricky part is fixing your tapelist
file--If you don't fix your tapelist, on the next run amanda will want
to use the tapes that you just labeled instead of continuing the current
cycle. The easy way to fix it is to take the date stamp from the last
tape in the cycle and change the "0" for all of the new tapes to that
date--and of course don't forget to adjust tapecycle and other
parameters in amanda.conf--and then amanda should finish the current
cycle before starting to use the new tapes.
Joseph Del Corso wrote:
Is it possible to amlabel an entire rack of tapes without
doing it manually for each tape?
Specifically I have roughly 35 tapes that I'd like to label
in some kind of automated fashion all at once. Besides writing
my own script (which would take time and more than likely a HECK of
a lot of debugging) is there an easier way to do this?
Is there any benefit to doing this?
--
"Jonathan F. Dill" ([EMAIL PROTECTED])
CARB Systems and Network Administrator
Home Page: http://www.umbi.umd.edu/~dill
#!/bin/tcsh -f
set i=2
while ($i 9)
set j=`awk '{split($2,a,"."); print a[2]}' dds4/tapelist | sort -n | tail -1`
@ j++
amlabel dds4 dds4.$j
mtx -f /dev/sg3 unload
mtx -f /dev/sg3 load $i
@ i++
end
set j=`awk '{split($2,a,"."); print a[2]}' dds4/tapelist | sort -n | tail -1`
@ j++
amlabel dds4 dds4.$j
mtx -f /dev/sg3 eject
amindexd java - unexpected EOF/unprocessed input
Hello ;-)
I tried to connect to the amindexd service via Java. It is possible
to read what the Server first barfs out... but if I try to send
some commands (SECURITY root, HOST localhost, etc.) nothing happens
and the debug output of amindexd says, that there is an unexpected EOF
and some unprocessed input (the mentioned commands I sent before).
=
This is what the /tmp/amanda/amindexd.debug says:
220 kant AMANDA index server (2.4.1p1) ready.
? unexpected EOF
? unprocessed input:
-
? SECURITY root
-
amindexd: pid 5867 finish time Thu Feb 15 17:27:19 2001
=
I also tried to get a connection via Telnet, but the socket-port
of the telnet process is always to high, to be taken as a secure port
by the amindexd. Do you know a possibility of setting a portrange
to a telnet process?
Well, please have a look at the following (attached) tiny java program
and give me some hints, how to get a connection to the amindexd.
I want to write some interface from Java to amindexd for providing
a possibility for writing native java programs to take use of
the Amanda Backup Service ;-)
Please sent me a copy (CC:) to my private account ( mailto:[EMAIL PROTECTED])
thanx in advance,
Sebastian
import java.net.InetAddress;
import java.net.Socket;
import java.io.InputStream;
import java.io.PrintWriter;
public class testsock {
public static String read(InputStream in) throws Exception {
StringBuffer sb = new StringBuffer();
while (true) {
String str = "";
while (in.available() 0) {
byte b[] = new byte[in.available()];
in.read(b);
str = new String(b);
sb.append(str);
}
if (str.indexOf("AMANDA") -1)
break;
else if (str.indexOf("5") -1)
break;
else if (str.indexOf("2") -1)
break;
}
return sb.toString();
}
public static void main(String args[]) throws Exception {
Socket s = new Socket("localhost", 10082, InetAddress.getLocalHost(), 1028);
System.out.println("localport: "+s.getLocalPort());
InputStream in = s.getInputStream();
System.out.println("got: "+read(in));
PrintWriter out = new PrintWriter(s.getOutputStream(), true);
System.out.println("send: SECURITY root");
out.println("SECURITY root");
System.out.println("got: "+read(in));
}
}
testsock.class
#!/usr/bin/perl
use Net::Telnet();
$hostname = "localhost";
$port = 10082;
$t = new Net::Telnet ( Host = $hostname, Port = $port);
$t-open("$hostname");
do
{
$data = $t-getline(Timeout = 40);
print "got: $data";
$t-print("SECURITY root\n");
} while (true);
Scripting question -- readstatus
First I'd like to thank everyone for their help with scripts, I recieved quite a few that were all excellent resources for creating my own. I have a tape rack that holds 35 tapes, and an robotic arm tape changer that picks up the tapes and sticks them in the tape drive(s). I modified chg-zd-mtx, specifically the readstatus line, to read like: usedslot=`$MTX -f /dev/sg3 status | sed -n 's/Data Transfer Element 0:Empty/-1/p;s/Data Transfer Element 0:Full (Storage Element \(.\) Loaded):VolumeTag = DNR\(.\)\(.\)\(.\)/\1/p'` This worked great!! For the first 9 tapes... and I realized why. In the previous line the number after Storage Element is read into ?variable? \(.\) - This represents one number. In order to go higher than 9 though I had to add a second \(.\) and a \2 so that it looks like: usedslot=`$MTX -f /dev/sg3 status | sed -n 's/Data Transfer Element 0:Empty/-1/p;s/Data Transfer Element 0:Full (Storage Element \(.\)\(.\) Loaded):VolumeTag = DNR\(.\)\(.\)\(.\)/\1\2/p'` My question is, is there a more elegant way (without scraping the whole script and trying a completely new one -- leading to more headaches and troubleshooting) to do what I'm trying to do? (i.e.-- read higher than one digit numbers, and possibly two digit -- though honestly I'm not at that point yet) As soon as I try and use this script to do any amcheck or dumping to the first 9 tapes, I'll have to revert everything back. Hope I explained this clearly enough, and that someone out there with more intelligence than I in scripting can help out. Joe
Sorry, another question -- eject
I'm also curious if there is a way to get around a problem I seem to have every now and then. Specifically, I can issue the mtx -f /dev/sg4 eject (sg4 being the first tape drive) and I will randomly get an error like this: [operator@lycan:/usr/local/etc/amanda/DailySet1]# mtx -f /dev/sg4 eject mtx:eject failed Now I can simply submit the eject command again and it will work, but I'm worried about trying to automate anything now because I'm not sure if I'll have problems with the eject command. Any thoughts? Joe
Re: Scripting question -- readstatus
I used this: \([1-9][0-9]*\) instead of: \(.\) It will give any number = 1. On Thu, 15 Feb 2001, Joseph Del Corso wrote: First I'd like to thank everyone for their help with scripts, I recieved quite a few that were all excellent resources for creating my own. I have a tape rack that holds 35 tapes, and an robotic arm tape changer that picks up the tapes and sticks them in the tape drive(s). I modified chg-zd-mtx, specifically the readstatus line, to read like: usedslot=`$MTX -f /dev/sg3 status | sed -n 's/Data Transfer Element 0:Empty/-1/p;s/Data Transfer Element 0:Full (Storage Element \(.\) Loaded):VolumeTag = DNR\(.\)\(.\)\(.\)/\1/p'` This worked great!! For the first 9 tapes... and I realized why. In the previous line the number after Storage Element is read into ?variable? \(.\) - This represents one number. In order to go higher than 9 though I had to add a second \(.\) and a \2 so that it looks like: usedslot=`$MTX -f /dev/sg3 status | sed -n 's/Data Transfer Element 0:Empty/-1/p;s/Data Transfer Element 0:Full (Storage Element \(.\)\(.\) Loaded):VolumeTag = DNR\(.\)\(.\)\(.\)/\1\2/p'` My question is, is there a more elegant way (without scraping the whole script and trying a completely new one -- leading to more headaches and troubleshooting) to do what I'm trying to do? (i.e.-- read higher than one digit numbers, and possibly two digit -- though honestly I'm not at that point yet) As soon as I try and use this script to do any amcheck or dumping to the first 9 tapes, I'll have to revert everything back. Hope I explained this clearly enough, and that someone out there with more intelligence than I in scripting can help out. Joe -- Jason Hollinden SMG Systems Admin
Re: Sorry, another question -- eject
This is from the FAQ that comes with mtx. It looks like the eject is for ejecting magazines from certain autoloaders, not tapes from drives. May be why it's only working some of the time. Does 'mtx -f /dev/sg4 unload slotnumber drive number' work? 8- Q: How do I eject the magazine of my autoloader? A: Many low-end DAT autoloaders support the removable media 'EJECT' command sent to the robotics device, even though it's not documented (or required) in the SCSI standards. If the loader is at /dev/sgb, simply do 'mtx -f /dev/sgb eject' and see what happens. (If nothing happens, your autoloader doesn't support 'eject'). Some high-end libraries have their own proprietary way for ejecting magazine trays, generally involving abuse of the 'transfer' command and 'eepos' addendums, but this is totally non-standard and undocumented. On Thu, 15 Feb 2001, Joseph Del Corso wrote: I'm also curious if there is a way to get around a problem I seem to have every now and then. Specifically, I can issue the mtx -f /dev/sg4 eject (sg4 being the first tape drive) and I will randomly get an error like this: [operator@lycan:/usr/local/etc/amanda/DailySet1]# mtx -f /dev/sg4 eject mtx:eject failed Now I can simply submit the eject command again and it will work, but I'm worried about trying to automate anything now because I'm not sure if I'll have problems with the eject command. Any thoughts? Joe -- Jason Hollinden SMG Systems Admin
Re: RedHat7.0 and Xinetd
"Sergio" == Sergio Pereira [EMAIL PROTECTED] writes:
Sergio Hi folks, I'm trying to use AMANDA 2.4.2p1 but some
Sergio problems are happening. So, first of all I need to know
Sergio how can I call amandad, amindexd and amidxtaped on xinetd
Here's my files, which work for me.
Ben
[/etc/xinetd.d/amanda]
# default: on
# description: The AMANDA backup client.
service amanda
{
socket_type = dgram
wait= yes
user= amanda
server = /usr/local/libexec/amandad
}
[/etc/xinetd.d/amandaidx]
# default: on
# description: The Amanda indexer.
service amandaidx
{
socket_type = stream
wait= no
user= amanda
server = /usr/local/libexec/amindexd
}
[/etc/xinetd.d/amidxtape]
# default: on
# description: The Amanda index/tape server.
service amidxtape
{
socket_type = stream
wait= no
user= amanda
server = /usr/local/libexec/amidxtaped
}
Re: Mixed output in amdump.n file
I have noticed that the amdump.n log file has mixed output from multiple sources in it at times - like from 'setup_estimate' a 'dumper.' Is this a known problem? ... Yes. That file contains the stdout/stderr messages from the various Amanda programs (e.g. printf/fprintf). There is no attempt to lock the output to protect against mixing it. Any plans to fix it? No. It would be a major overhaul to find all those places. And some of them are not even under our control (e.g. when we fire off an external tape changer program). Michael Russell John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Pre-compiled Sun 2.5.1 binaries?
I am having difficulty installing Amanda on one of our older, but more critical production machines. Basically, it will not compile - I've tried re-installed gcc, but something is seriously messed. Unfortunately it is a production machine, so there is only so much I can do. Anyway, does anyone know where I can find a pre-compiled version of Amanda for SunOS 5.5.1 (sparc)? Thanks! Steve
Re: Amrecover Problem, amandahostauth problem in amidxtaped.debug
bsd security: remote host stanley.domain.org user root local user amanda ... But on hall the common-src/security program produces the following : Remote user: amanda You need to give ./security "root" as the remote user, not "amanda", then see what it has to say. I seem to recall seeing some problems in the parsing code with trailing whitespace, so you might check for that in the file. Friedrich John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: AMRECOVER: NEED HELP!!!
amrestore: fast-forward: Errore di input/output
Assuming I can translate this properly :-), this means the drive reported
an I/O error to the OS (who reported it to Amanda who logged it).
In other words, the tape could not be read.
But all may not be lost. Here are some things to try:
* Find out what file on the tape holds the image you want. Use amtoc
or "amadmin config find host disk". Once you know that,
rewind the tape do a single fsf to that file and try the amrecover
again if the fsf works.
* Try retensioning the tape ("mt retension" or something like that
-- you'll have to look it up in your OS documentation), if the drive
supports that.
* Try cleaning the drive.
Carlo Alberto
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: REF: Start and stop time
How can I tell when a dumper and taper starts and stops. Get this: ftp://gandalf.cc.purdue.edu/pub/amanda/amdumpts and run it against an amdump.NN log file. It looks at the start time and converts the delta timestamps into a time of day. Then look for FILE-DUMP or PORT-DUMP for dumper start and FILE-WRITE or PORT-WRITE for taper start. Look for the matching DONE to find out when it finished. Robert John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amadmin 2.4.1 is too permissive when matching file system names
I am trying to restore some files from machine hawk file system /u1. I get a lot of matches which really aren't helpful. [route@kite B]# /usr/local/pkgs/amanda-2.4.1p1.server/sbin/amadmin ssli find hawk /u1 Scanning /bkup... date host disk lv tape or file file status 2001-01-24 hawk /u1 1 ssli-013 37 OK 2001-01-25 hawk /u1 1 ssli-014 36 OK 2001-01-26 hawk /u1 1 ssli-015 44 OK 2001-01-27 hawk /u1 1 ssli-016 43 OK 2001-01-28 hawk /u1 1 ssli-017 41 OK 2001-01-29 hawk /u1 1 ssli-018 43 OK 2001-01-30 hawk /u1 1 ssli-020 55 OK 2001-01-31 hawk /u1 0 ssli-019 50 OK 2001-02-01 hawk /u1 1 ssli-0214 OK 2001-02-02 hawk /u1 1 ssli-0006 OK 2001-02-03 hawk /u1 1 ssli-0013 OK 2001-02-04 hawk /u1 1 ssli-002 35 OK 2001-02-06 hawk /u1 1 ssli-004 69 OK 2001-02-07 hawk /u1 0 ssli-005 72 OK 2001-02-08 hawk /u1 1 ssli-006 28 OK 2001-02-09 hawk /u1 1 ssli-007 26 OK 2001-02-10 hawk /u1 1 ssli-0082 OK 2001-02-11 hawk /u1 1 ssli-009 31 OK 2001-02-12 hawk /u1 1 ssli-010 38 OK 2001-02-13 hawk /u1 1 ssli-011 36 OK 2001-02-14 hawk /u1 1 ssli-012 38 OK 2001-01-24 hawk /u15 1 ssli-013 11 OK 2001-01-25 hawk /u15 1 ssli-014 10 OK 2001-01-26 hawk /u15 1 ssli-015 15 OK 2001-01-27 hawk /u15 1 ssli-016 11 OK 2001-01-28 hawk /u15 1 ssli-017 12 OK 2001-01-29 hawk /u15 0 ssli-018 12 OK 2001-01-30 hawk /u15 1 ssli-020 13 OK 2001-01-31 hawk /u15 1 ssli-019 11 OK 2001-02-01 hawk /u15 1 ssli-021 12 OK 2001-02-02 hawk /u15 1 ssli-000 14 OK 2001-02-03 hawk /u15 1 ssli-001 13 OK 2001-02-04 hawk /u15 1 ssli-002 10 OK 2001-02-06 hawk /u15 0 ssli-004 13 OK 2001-02-07 hawk /u15 1 ssli-005 12 OK 2001-02-08 hawk /u15 1 ssli-006 13 OK 2001-02-09 hawk /u15 1 ssli-007 11 OK 2001-02-10 hawk /u15 1 ssli-008 10 OK 2001-02-11 hawk /u15 1 ssli-009 12 OK 2001-02-12 hawk /u15 1 ssli-010 12 OK 2001-02-13 hawk /u15 0 ssli-011 14 OK 2001-02-14 hawk /u15 1 ssli-012 15 OK 2001-01-24 hawk /u17 1 ssli-0139 OK 2001-01-25 hawk /u17 1 ssli-0147 OK 2001-01-26 hawk /u17 1 ssli-015 11 OK 2001-01-27 hawk /u17 1 ssli-0167 OK 2001-01-28 hawk /u17 1 ssli-0177 OK 2001-01-29 hawk /u17 0 ssli-018 10 OK 2001-01-30 hawk /u17 1 ssli-020 12 OK 2001-01-31 hawk /u17 1 ssli-0198 OK 2001-02-01 hawk /u17 1 ssli-021 11 OK 2001-02-02 hawk /u17 1 ssli-000 13 OK 2001-02-03 hawk /u17 1 ssli-001 12 OK 2001-02-04 hawk /u17 1 ssli-0029 OK 2001-02-06 hawk /u17 0 ssli-0049 OK 2001-02-07 hawk /u17 1 ssli-005 10 OK 2001-02-08 hawk /u17 1 ssli-006 10 OK 2001-02-09 hawk /u17 1 ssli-007 10 OK 2001-02-10 hawk /u17 1 ssli-0086 OK 2001-02-11 hawk /u17 1 ssli-0098 OK 2001-02-12 hawk /u17 1 ssli-0108 OK 2001-02-13 hawk /u17 0 ssli-0117 OK 2001-02-14 hawk /u17 1 ssli-0128 OK [route@kite B]# -- Jeff Silverman, sysadmin for the Research Computing Systems (RCS) University of Washington, School of Engineering, Electrical Engineering Dept. Box 352500, Seattle, WA, 98125-2500 FAX: (206) 221-5264 Phone (206) 543-9378 [EMAIL PROTECTED] http://rcs.ee.washington.edu/~jeffs
Re: amadmin 2.4.1 is too permissive when matching file system names
On Thu, 15 Feb 2001, Jeff Silverman wrote: I am trying to restore some files from machine hawk file system /u1. I get a lot of matches which really aren't helpful. [route@kite B]# /usr/local/pkgs/amanda-2.4.1p1.server/sbin/amadmin ssli find hawk /u1 From 'man amadmin' : Disks are regular expressions, so "sd0" will match disks "sd0a" and "sd0g" and "/mnt" will match "/mnt", "/mnt/a", and "/mnt/b". To match only "/mnt", use "^/mnt$". This is the same mechanism used by amrestore(8). -Mitch
amrestore problem
Hi! I will restore some files from the tape changer, but i become some errors: root@fileserver:/usr/local/sbin ./amrestore /dev/sg5 king amrestore: error reading file header: the argument is not correct (Das Argument ist ungueltig) In chg-scsi.conf i have config 0 drivenum0 dev /dev/nst0 scsitapedev /dev/sg5 startuse0 enduse 9 Why don't work amrestore? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Can you set eject keyword with chg-chio?
Hello, I have an ADIC 1200E autoloader, and chio works great manually (FreeBSD system). I'm setting up AMANDA, and was doing the testing with amtape as suggested in "the amanda chapter". My particular autoloader requires that you do an "mt offl" (eject) before it is able to "chio move drive 0 slot n". I dug around in the mail archives for a while, but it seems that only chg-multi and chg-scsi even use config files. Looking at the actual chg-chio.pl perl script confirmed that there is no option for issuing an eject first. How might I go about doing this? Thanks, -Paul -- Paul D. Schmidt | [EMAIL PROTECTED] Coder / Sys Admin |[EMAIL PROTECTED] Unbound Communications | http://www.unboundcom.com "The grass may actually be greener on the other side of the fence, but it still has to be mowed." --Anonymous
