I just upgraded to Amanda 3.1.1 using the provided RPM. The system is CentOS
5.4 x86_64 and is connected to a Dell ML6000 changer. I was using the
chg-zd-mtx script previously and moved to the new chg-robot driver for the new
install. I did a full update to get an inventory, but I still seem to
track.
Thanks,
Mike
On Jul 23, 2010, at 1:15 PM, Dustin J. Mitchell wrote:
On Fri, Jul 23, 2010 at 2:07 PM, Michael Robbert mrobb...@mines.edu wrote:
1. How can we fix the fatal error? I'm more than willing to help debug if
this doesn't appear to be reproducible. I'm a capable Linux system
I use the PV122T, is that close enough. Why?
Mine is the DLT version w/o barcodes if that makes any difference to
you.
On Wed, Mar 05, 2003 at 04:25:09PM +0100, Said El Mamouni wrote:
hi,
does someone use a powervault 120t on à linux redhat 8 ?
thanks
S.El Mamouni
--
Michael Murph
On Thu, Feb 13, 2003 at 10:41:40AM -0500, Jon LaBadie wrote:
Gene Heskett wrote:
It can take a very short time to read 32KB, that is all that is done.
Does your tapelist file show all the tapes you labeled?
Can you manually do manipulate the changer, load each slot in turn
and run
Gene Heskett wrote:
On Wednesday 12 February 2003 19:23, Michael Robbert wrote:
Here is an update on the problem that I sent yesterday. I had
entered my DDS4backup into cron and last night the backup
actually worked, sort of. It looks like it wrote to the tape in
slot one, which I labeled
Here is an update on the problem that I sent yesterday. I had entered my
DDS4backup into cron and last night the backup actually worked, sort of.
It looks like it wrote to the tape in slot one, which I labeled
DDS4backup01, but the report says that it was labeled DDS4backup05.
Below you'll find
I have two amanda configurations for two different tape changers and
when I run amtape or amlabel on one them the labels are not read from
the tapes, but seemingly taken from memory somewhere.
The changer this isn't working is an HP SureStore 24x6 that used to work
fine until I had to re-do the
Yes, amcheck is happy.
Here is the full Email I get with the following disklist(I don't
get any detail section at the end):
client /varroot-tar
##
These dumps were to tape DailySet102.
The next 5 tapes Amanda expects to used
John,
I didn't find any core files anywhere on the client or server. At
least anywhere that Amanada would have anything to do with. Here
are all the references to dumper#, I don't see anything that
jumps out at me and I am pretty sure that the problem is on the
client side where the tar seems to
John,
It looks like the RPM isn't the issue after all. That makes me
happy. The ulimit command showed me that I had a 100Mb limit on
any file size. I'll have to check it out, but my guess is that
the Bastille hardening script did that for me. This was the first
system that I had tried that on. I
I am trying to get AMANDA working for the first time and am stuck
getting amdump to complete with all my partitions. I have tracked the
problem down to this error at the end of the sendbackup.debug file on
the client:
error [/bin/tar got signal 13]
The error changes slightly if I change the
11 matches
Mail list logo
