tapeless with amanda-242-tapeio problem
Hi, I'm intending to use tapeless backup to my hard drive. From the mailing list, I see that I can use 2.4.2 (CVS amanda-242-tapeio) or 2.4.3 method. Which one is a better choice for production? Due to some mail that explained the 2.4.2 method in detail, I'm currently trying to use it. I've set the amanda.conf, changer.conf, tape directory as in http://groups.yahoo.com/group/amanda-users/message/36136 However, when I'm at step 5 of the posting above (labelling), I get this error: amlabel: could not load slot "1": chg-multi: slot is empty Anyone can help me?
Re: amdump and tar don't work
> Brandon D. Valentine wrote: > > > You must give tar directory names, not disk devices. Rather than > /dev/da0s1e you need to tell tar to backup /var or whereever that > partition happens to be mounted. Modify your disklist to reflect this. > I also tried using the mountpoint, but I get the same message as before FAILURE AND STRANGE DUMP SUMMARY: samson.hei /var lev 0 FAILED [disk /var offline on samson.heitec.net?] I think it has something to do with tar, but I don't know how and where to edit the config files. I'm still reciving the messages that runtar "[must be invoked by operator]".
[[writing file: Input/output error]]. [out of tape]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
I have been using amanda for a few months without any problems but suddenly i
encountered a few. I do a level 0 dump everyday for all the machines on the
local network. There was no problem of "out of tape" before. I was hit with
the "out of tape" problem yesterday. So today i tested amanda again but this
time just dumping the localhost which is about 8gb of data. But it still
fails with the same error. This is my tapetype in amanda.conf
-
define tapetype daily {
comment "just produced by tapetype program"
length 34798 mbytes
filemark 152 kbytes
speed 2578 kbytes
-
I have also tried cleaning the drive a few times because when the dump fails,
the orange light will start blinking. I also found something in the
/var/log/messages, here it is.
-
Aug 13 03:06:37 marvin kernel: st0: Error with sense data: Info fld=0x8000,
Deferred st09:00: sns = f1 3
Aug 13 03:06:37 marvin kernel: ASC=80 ASCQ= 1
Aug 13 03:06:37 marvin kernel: Raw sense data:0xf1 0x00 0x03 0x00 0x00 0x80
0x00 0x16 0x00 0x00 0x1c 0x0d 0x80 0x01 0x00 0x00
0x00 0x00 0x83 0x01 0xb1 0x00 0x00 0x16 0xd3 0x00 0x94 0x66 0x17 0x00
Aug 13 03:06:37 marvin kernel: st0: Error with sense data: Info fld=0x1,
Current st09:00: sns = f0 3
Aug 13 03:06:37 marvin kernel: ASC= c ASCQ= 0
Aug 13 03:06:37 marvin kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x00 0x00
0x01 0x16 0x00 0x00 0x1c 0x0d 0x0c 0x00 0x00 0x00
0x00 0x00 0x83 0x01 0xb1 0x00 0x00 0x16 0xd3 0x00 0x94 0x66 0x17 0x00
Aug 13 03:06:37 marvin kernel: st0: Error on write filemark.
-
Below is the mail that i get from amanda.
-
These dumps were to tape week2.
*** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
localhost /dev/hda2 lev 0 STRANGE
localhost /dev/hda2 lev 0 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:03
Run Time (hrs:min) 0:42
Dump Time (hrs:min)0:28 0:28 0:00
Output Size (meg)2593.2 2593.20.0
Original Size (meg) 5386.4 5386.40.0
Avg Compressed Size (%)48.1 48.1--
Filesystems Dumped1 1 0
Avg Dump Rate (k/s) 1565.9 1565.9--
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
FAILED AND STRANGE DUMP DETAILS:
/-- localhost /dev/hda2 lev 0 STRANGE
sendbackup: start [localhost:/dev/hda2 level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./var/spool/cups/c02102: Warning: Cannot stat: No such file or
directory
| Total bytes written: 5648015360 (5.3GB, 3.2MB/s)
sendbackup: size 5515640
sendbackup: end
\
NOTES:
planner: Last full dump of localhost:/dev/hda2 on tape overwritten in 1
run.
planner: Preventing bump of localhost:/dev/hda2 as directed.
taper: tape week2 kb 231424 fm 1 writing file: Input/output error
driver: going into degraded mode because of tape error.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
- -- -
localhost/dev/hda2 0 55156402655488 48.1 28:161565.9 N/A N/A
(brought to you by Amanda version 2.4.2p2)
-
I have no idea why it starts to fail now but not before, is it a hardware
problem? Appriciate any suggestions from you guys. Please tell me what more
do i need to include.
Thanks and regards
junaidi
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9WB4fInIYkBVpGqURAqAYAJ4o6Xr3q4PMg2lR7ISrMKzVX8ddJgCfWbCW
KLjbnqK7XQ4ZS0Kj9poyyKw=
=5b8V
-END PGP SIGNATURE-
Re: [[writing file: Input/output error]]. [out of tape]
Sounds a lot like when my DLT failed last week. I got a few of the same errors. I
has Sun replace it and all is well once again. Good Luck!
adi wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello
> I have been using amanda for a few months without any problems but suddenly i
> encountered a few. I do a level 0 dump everyday for all the machines on the
> local network. There was no problem of "out of tape" before. I was hit with
> the "out of tape" problem yesterday. So today i tested amanda again but this
> time just dumping the localhost which is about 8gb of data. But it still
> fails with the same error. This is my tapetype in amanda.conf
> -
> define tapetype daily {
> comment "just produced by tapetype program"
> length 34798 mbytes
> filemark 152 kbytes
> speed 2578 kbytes
> -
> I have also tried cleaning the drive a few times because when the dump fails,
> the orange light will start blinking. I also found something in the
> /var/log/messages, here it is.
> -
> Aug 13 03:06:37 marvin kernel: st0: Error with sense data: Info fld=0x8000,
> Deferred st09:00: sns = f1 3
> Aug 13 03:06:37 marvin kernel: ASC=80 ASCQ= 1
> Aug 13 03:06:37 marvin kernel: Raw sense data:0xf1 0x00 0x03 0x00 0x00 0x80
> 0x00 0x16 0x00 0x00 0x1c 0x0d 0x80 0x01 0x00 0x00
> 0x00 0x00 0x83 0x01 0xb1 0x00 0x00 0x16 0xd3 0x00 0x94 0x66 0x17 0x00
> Aug 13 03:06:37 marvin kernel: st0: Error with sense data: Info fld=0x1,
> Current st09:00: sns = f0 3
> Aug 13 03:06:37 marvin kernel: ASC= c ASCQ= 0
> Aug 13 03:06:37 marvin kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x00 0x00
> 0x01 0x16 0x00 0x00 0x1c 0x0d 0x0c 0x00 0x00 0x00
> 0x00 0x00 0x83 0x01 0xb1 0x00 0x00 0x16 0xd3 0x00 0x94 0x66 0x17 0x00
> Aug 13 03:06:37 marvin kernel: st0: Error on write filemark.
> -
>
> Below is the mail that i get from amanda.
> -
> These dumps were to tape week2.
> *** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
> Some dumps may have been left in the holding disk.
> Run amflush to flush them to tape.
> The next tape Amanda expects to use is: a new tape.
>
> FAILURE AND STRANGE DUMP SUMMARY:
> localhost /dev/hda2 lev 0 STRANGE
> localhost /dev/hda2 lev 0 FAILED [out of tape]
>
> STATISTICS:
> Total Full Daily
>
> Estimate Time (hrs:min)0:03
> Run Time (hrs:min) 0:42
> Dump Time (hrs:min)0:28 0:28 0:00
> Output Size (meg)2593.2 2593.20.0
> Original Size (meg) 5386.4 5386.40.0
> Avg Compressed Size (%)48.1 48.1--
> Filesystems Dumped1 1 0
> Avg Dump Rate (k/s) 1565.9 1565.9--
>
> Tape Time (hrs:min)0:00 0:00 0:00
> Tape Size (meg) 0.00.00.0
> Tape Used (%) 0.00.00.0
> Filesystems Taped 0 0 0
> Avg Tp Write Rate (k/s) -- -- --
>
> FAILED AND STRANGE DUMP DETAILS:
>
> /-- localhost /dev/hda2 lev 0 STRANGE
> sendbackup: start [localhost:/dev/hda2 level 0]
> sendbackup: info BACKUP=/bin/tar
> sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... -
> sendbackup: info COMPRESS_SUFFIX=.gz
> sendbackup: info end
> ? gtar: ./var/spool/cups/c02102: Warning: Cannot stat: No such file or
> directory
> | Total bytes written: 5648015360 (5.3GB, 3.2MB/s)
> sendbackup: size 5515640
> sendbackup: end
> \
>
> NOTES:
> planner: Last full dump of localhost:/dev/hda2 on tape overwritten in 1
> run.
> planner: Preventing bump of localhost:/dev/hda2 as directed.
> taper: tape week2 kb 231424 fm 1 writing file: Input/output error
> driver: going into degraded mode because of tape error.
>
> DUMP SUMMARY:
> DUMPER STATSTAPER STATS
> HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
> - -- -
> localhost/dev/hda2 0 55156402655488 48.1 28:161565.9 N/A N/A
>
> (brought to you by Amanda version 2.4.2p2)
> -
>
> I have no idea why it starts to fail now but not before, is it a hardware
> problem? Appriciate any suggestions from you guys. Please tell me what more
> do i need to include.
>
> Thanks and regards
> junaidi
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iD8DBQE9WB4fInIYkBVpGqURAqAYAJ4o6Xr3q4PMg2lR7ISrMKzVX8ddJgCfWbCW
> KLjbnqK7XQ4ZS0Kj9poyyKw=
> =5b8V
> -EN
SGI IRIX xfsrestore
The header at the beginning of the amanda dump file says to restore use dd if= bs=32k skip=1 | /sbin/xfsrestore -f... - However, this is producing errors from xfsrestore. If you have used a dd into a piped xfsrestore under SGI IRIX, could you email me the command? amanda 2.4.1p1 TIA, Anne Hammond, University of Colorado at Boulder [EMAIL PROTECTED]
Re: using Netcat as a wrapper on solaris
>On Thursday 08 August 2002 14:07, Adam D. Read wrote: >>Inetd, Xinetd are not options for me to use on my solaris boxen. >Sorry, I missed that solaris thing. Huh? xinetd should run just fine on SunOS 5.
Re: SGI IRIX xfsrestore
* Anne M. Hammond ([EMAIL PROTECTED]) [20020812 18:54] thus spake: > The header at the beginning of the amanda dump file says > to restore use > dd if= bs=32k skip=1 | /sbin/xfsrestore -f... - > > However, this is producing errors from xfsrestore. and these would be? > > If you have used a dd into a piped xfsrestore under > SGI IRIX, could you email me the command? Not sure if this will help you, but digging from my notes when I was using amanda-2.4.1p1 with xfsdump/xfsrestore on O200's running irix-6.4 (a long time ago!): amrecover does not have the capability to interface correctly with xfsrestore with the present version (2.4.1p1). You have to use the following command: rsh -n -l amrestore -p \ [] [] | xfsrestore -ib 2 - . where should all be replaced with proper values. Values in brakets are not mandatory. The xfsrestore flags have to be typed *exactly as shown*. Don't forget to position the tape head correctly! xfsrestore used to be very picky about its arguments, spaces. etc... What version of irix are you running? YMMV, jf > > amanda 2.4.1p1 > > TIA, > Anne Hammond, University of Colorado at Boulder > [EMAIL PROTECTED] -- Fill what's empty. Empty what's full. Scratch where it itches.
