Hi Dustin
-Original Message-
From: owner-amanda-us...@amanda.org
[mailto:owner-amanda-us...@amanda.org] On Behalf Of Dustin J. Mitchell
Sent: Wednesday, October 06, 2010 6:03 PM
To: amanda-users@amanda.org
Subject: Re: FW: amrecover bug?
On Wed, Oct 6, 2010 at 10:10 AM, Jon
just an update. tested this for the past 2 days, everything is working fine.
+--
|This was sent by richard.t@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
On Thu, Oct 7, 2010 at 1:49 AM, Titl Erich erich.t...@ruf.ch wrote:
I guess this finding should give you something to chew on
Indeed! If I'm reading the hex dumps correctly, then, the first file
is padded at the beginning with exactly 28424 bytes of zero. The file
lengths differ by the same
Dustin,
I got the same error lastnight.
hertz /gauss/export/users-j lev 3 partial taper: Error writing block:
Mysterious short write on tape device: Tried 2097152, got 1052672
hertz /gauss/export/users-s lev 4 FLUSH while ejecting volume: Can't open
tape device /dev/rmt/0cbn: Device busy
On Thu, Oct 7, 2010 at 11:01 AM, McGraw, Robert P rmcg...@purdue.edu wrote:
I had been using 2048KB, which I had defined in tapetype, when I was
running Amanda 2.x and never got this error.
Yes, it's a new error for something that used to be handled quietly.
Basically, the kernel takes the
