0
>
> gzip: stdin: unexpected end of file
> /bin/tar: 186 garbage bytes ignored at end of archive
> /bin/tar: Unexpected EOF in archive
> /bin/tar: Error is not recoverable: exiting now
> 64+0 records in
> 64+0 records out
>
> amverify DailySet1
> Wed Aug 1 22:27:14
>am i correct that amanda will not dump a disk that has an
>estimate larger than the tape size, correct? ...
No, that's not quite correct. If you have a changer and runtapes > 1,
it will go ahead and dump things bigger than a single tape.
>i presume this is
>because amanda has no way of reliab
am i correct that amanda will not dump a disk that has an
estimate larger than the tape size, correct? i presume this is
because amanda has no way of reliably predicting whether or not
the disk will fit on the disk *after* compression, which of
course, it may be able to do quite easily. can this
>I keep getting this error:
>
>tuttle sda1 lev 1 FAILED [no more holding disk space]
>
>What is the problem.
You're running Amanda in degraded mode, i.e. no tape is in the drive,
or it had an error, or something along those lines, and Amanda has run
out of holding disk space to do any more dumps.
hello again,
i found the culprit. a dns change caused the problem. someone changed the
name of the IP my amanda server sat on. i use /etc/hosts.allow to grant
access to the amandad service. since the dns entry changed, and the name
that came up was not authorized in hosts.deny, amanda was ret
hello all,
i'm running amanda v2.4.2p2 on a linux RH v7.1 box. it's been running quite
smoothly for about two weeks now, however, today `amcheck -c ` started
failing the self-check (host down? error).
the configuration on the box has not changed and the tmp file in /tmp/amanda
doesn't give any
>What would be really neat (bordering on total perfection) is if you could
>have a single disklist, and have it shared over multiple tapedrives.
>But I guess you're gonna tell me that that will be in 2.4.2p3 ;)
That's one of the items scheduled the taper rewrite. Not 2.4.2p3,
more like 2.8234672
* John R. Jackson <[EMAIL PROTECTED]> (Tue, Jul 31, 2001 at 12:44:19PM -0500)
>>the thing is that it's a taperobot/tapechanger, and I remember reading
>>discussions that getting that to work is not always a trivial issue.
> That's going to be true no matter what. Any time software comes in
> cont
* Brian Cuttler <[EMAIL PROTECTED]> (Wed, Aug 01, 2001 at 10:41:55AM -0400)
> John,
> No hardware changes, problems began with the OS upgrade, checked
> all the cables. We can actually perform amdump just fine as long
> as the tape was labeled before the OS upgrade.
> Yes, amanda hitting the ten
* John R. Jackson <[EMAIL PROTECTED]> (Wed, Aug 01, 2001 at 09:15:32AM -0500)
>>I do not know the mechanism for "labeling" but wanted to
>>describe the process for SGI. ...
> The sequence is (and yes, all those rewinds look a bit silly now that
> I write it all down :-):
> open
> rewind
>
For what it's worth, I haven't seen this with my tape drive yet, but my
old Indigo began having some SCSI buss timeouts and errors on the
external cdrom after upgrading to 6.5.12m. I checked the comp.sys.sgi*
newsgroups and didn't see anything there yet about it. It may be a
driver issue with th
John,
No hardware changes, problems began with the OS upgrade, checked
all the cables. We can actually perform amdump just fine as long
as the tape was labeled before the OS upgrade.
Yes, amanda hitting the tender spots as opposed to Amanda being
the problem. I'm trying to make that exact point
>We have been carrying the amanda.conf foward from one version
>to the next. I don't know what the initial version was, perhaps
>2.6 ? ...
Only if you're in a time warp and living about a decade in the future :-).
My guess is you're trying to upgrade from 2.3, but I never ran that
(it was years
John,
> >We have been carrying the amanda.conf foward from one version
> >to the next. I don't know what the initial version was, perhaps
> >2.6 ? ...
er, 2.2.6 perhaps ?
We have been running 2.4.x for a while and recently upgraded
to 2.4.2p2 for "chunksize" which has been invaluable for us.
>I meant I believe that our version which is 2.4.2p2 was current.
>
>The query was on "current" rather than the version number I reported.
If I understand what you're asking, yes, 2.4.2p2 is the current stable
release. There have been some patches since then, but nothing in the
tape area (or at
>We are seeing bus errors and timeouts that we didn't see
>under the earlier version of IRIX.
Ah, I see.
Amanda is a purely application level program that makes normal system
calls. It cannot be the cause of these types of errors, although it might
instigate them (along the lines of a text edit
John,
We are seeing bus errors and timeouts that we didn't see
under the earlier version of IRIX.
I can pull the errors from the SYSLOG file if you'd like.
I was trying though to figure out, and relay the info to SGI,
why label was failing and writing the dumps was working. I
don't have enough
John,
We have been carrying the amanda.conf foward from one version
to the next. I don't know what the initial version was, perhaps
2.6 ? This server (a different server from the 6.5.12 upgrade
problem) is also running 2.4.2p2.
What are the correct entries ?
> >Looking at the amanda.conf file
>is it possible to force an active tape to be use??
I'm sure you already realize the bad situation you're in with only one
tape. If that tape fails, or if anything at all bad happens during the
Amanda run, you will have lost all chance of recovering anything that
didn't make it to tape on that r
>Looking at the amanda.conf file on one of my servers I see this
>
>diskdir "/usr4/amanda/work" # added temporary holding area to speed
>disksize 3000 MB # things up ... -ck 10-12-00
>diskdir "/usr22/amanda/work"# where the holding disk is
>disksize 2000 MB # ho
>Unfortunately we are unable to label the tape # amlabel -f
>at any either 35gig or 40 gig density. ...
Ummm, that's not anywhere near enough information to go on. What version
of Amanda? What, exactly did you put on the command line? What did
it say? Why do you think it didn't work?
>I do
Hello amanda users,
We have been supporting our DLT8000 by treating it as a DLT7000
under IRIX 6.5.(3-7)m and modifying the scsi device tables.
We recently upgraded to 6.5.12m which "supports" DLT8000 via
the new "ts" class device driver.
Unfortunately we are unable to label the tape # amlabel
Amanda users,
Looking at the amanda.conf file on one of my servers I see this
diskdir "/usr4/amanda/work" # added temporary holding area to speed
disksize 3000 MB # things up ... -ck 10-12-00
diskdir "/usr22/amanda/work"# where the holding disk is
disksize 2000 MB
is it possible to force an active tape to be use??
Because i have 3 tapes in rotation(dump everyday on
HD with one flush per week) and during few week i
have only just one (my boss has gone on holiday with
2 tapes :pp).
thx for advance.
__
24 matches
Mail list logo
