Jean-Francois Malouin wrote:
However amadmin info' still reports only one tape at level 0.
Is this the expected behaviour?
It's expected behavior, 'amadmin info' reports only the tape for the
last PART.
Jean-Louis
Replying to myself...see at the bottom...
* Jean-Francois Malouin [EMAIL PROTECTED] [20080305 11:30]:
Ok, here I go again. amanda-2.5.2p1 server and client debian/etch.
I have seen this in the past (last Oct iirc) and I remember that
Jean-Louis provided me with a patch but that was for the
Anyone on this please?
I know, it's not as sexy as 2.6.x :)
* Jean-Francois Malouin [EMAIL PROTECTED] [20080305 12:30]:
Ok, here I go again. amanda-2.5.2p1 server and client debian/etch.
I have seen this in the past (last Oct iirc) and I remember that
Jean-Louis provided me with a patch but
On Thu, Mar 6, 2008 at 12:24 PM, Jean-Francois Malouin
[EMAIL PROTECTED] wrote:
Anyone on this please?
I know, it's not as sexy as 2.6.x :)
I'm confused. I was hoping someone else understood the problem and would reply.
# /opt/amanda/sbin/amfetchdump -p -d /dev/nrst0 left1 \
bigbrain
Bcc:
Subject: Re: [bis] discrepency between amadmin, logs and tape content?
Reply-To:
In-Reply-To: [EMAIL PROTECTED]
* Dustin J. Mitchell [EMAIL PROTECTED] [20080306 13:56]:
On Thu, Mar 6, 2008 at 12:24 PM, Jean-Francois Malouin
[EMAIL PROTECTED] wrote:
Anyone on this please?
I know
Jean-Francois,
It's a known bug in amrecover, (will be fixed in 2.6.0b3). it try to
recover from dump even if not all part are available.
From amdadmin, only part 158, 159 and 160 are available.
You said all the parts are available on tapes, but why amadmin doesn't
list them?
Did it gives
Ok, here I go again. amanda-2.5.2p1 server and client debian/etch.
I have seen this in the past (last Oct iirc) and I remember that
Jean-Louis provided me with a patch but that was for the case of a
succesfully retried DLE.
In this particular case there was no retry but nevertheless amadmin
and
Jean-Francois Malouin wrote:
* Jean-Louis Martineau [EMAIL PROTECTED] [20071030 10:40]:
This bug is fixed in 2.5.3alpha, but the patch was not backported to
2.5.2p1.
Can you try the attached patch?
Looks like the patch did it.
amadmin now reports correctly and amfetchdump can
* Jean-Louis Martineau [EMAIL PROTECTED] [20071030 10:40]:
This bug is fixed in 2.5.3alpha, but the patch was not backported to
2.5.2p1.
Can you try the attached patch?
Looks like the patch did it.
amadmin now reports correctly and amfetchdump can restore the dump.
Thanks!
jf
This bug is fixed in 2.5.3alpha, but the patch was not backported to
2.5.2p1.
Can you try the attached patch?
Jean-Louis
Jean-Francois Malouin wrote:
Hi,
With amanda-2.5.2p1 I did an archive a few days ago and trying to
restore it caused me a few problems: amfetchdump tells me that
there is
Hi,
With amanda-2.5.2p1 I did an archive a few days ago and trying to
restore it caused me a few problems: amfetchdump tells me that
there is no valid data to be restored for that date and amadmin
reports a connection timeout:
grumpy: /opt/amanda/sbin/amfetchdump -p -d /dev/nst1
11 matches
Mail list logo