Toralf Lund wrote:
Paul Bijnens wrote:
Toralf Lund wrote:
Other possible error sources that I think I have eliminated:
1. tar version issues - since gzip complains even if I just uncopress
and send the data to /dev/null, or use the -t option.
2. Network transfer issues. I get errors even
[EMAIL PROTECTED] wrote:
On Thu, Nov 04, 2004 at 04:11:18AM -0500, foo wrote:
I was wrong, it turns out to be ip_conntrack_amanda from netfilter
that's the culprit. I haven't tested yet, but others have confirmed it.
I thought that was fixed in kernel 2.6.6 or did it break again? See:
Erik Anderson writes:
- On Thu, 04 Nov 2004 15:36:05 -0600, Frank Smith [EMAIL PROTECTED] wrote:
- Also, while sg is the proper device to use to control the changer,
- it doesn't understand tape commands like rewind, so make sure your
- tape device is referencing an st device (of course, your
- Original Message -
From: Eric Siegerman [EMAIL PROTECTED]
On Thu, Nov 04, 2004 at 09:57:52AM +0100, Paul Bijnens wrote:
Flynn wrote:
Amdump sometimes goes crazy apparently eating up all the machine
resources
and I can't get any access to anything when this happens, because I
Hi again,
i would bet it is a permision-problem, but i have no experience with
autogenerated device-nodes like yours.
Erik Anderson schrieb:
On Thu, 4 Nov 2004 14:51:54 -0600, Erik Anderson [EMAIL PROTECTED] wrote:
Okay - here's the deal. My /dev/sg* entries are symlins. They're
pointing as
Erik Anderson wrote:
Yes it does. Well maybe. /dev/sg1 (my changer) and /dev/sg2 (my tape
drive) are symlinks. The symlinks themselves don't have the correct
permissions, but the targets of the symlinks do have the correct
permissions.
I have nada experience with a changer, but I believe that
Dan Brown wrote:
This may be a problem then as the IDE holding disk is NFS mounted from a
third machine. The server with the backup is a SCSI only system and
doesn't support IDE.
That's bad indeed, unless you have gigabit ethernet (and even then maybe
not).
drive (+$700CDN / 80GB?!) nor
Flynn wrote:
Here is what I got from last night's run - it didn't fail, but there is
somehow a clue right there :
09:16:04 up 23:18, 1 user, load average: 4.34, 4.45, 4.29
59 processes: 57 sleeping, 2 running, 0 zombie, 0 stopped
CPU states: 0.9% user 29.8% system 0.0% nice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear all,
After compiling by hand and patching amcheck.c to include our signature, all
tests ran fine, backup work to tape etc, but a strange problem with amcheck:
quote
Appserv Tape Server Host Check
- -
Holding
On Fri, Nov 05, 2004 at 10:12:25AM +0100, Paul Bijnens wrote:
[EMAIL PROTECTED] wrote:
On Thu, Nov 04, 2004 at 04:11:18AM -0500, foo wrote:
I was wrong, it turns out to be ip_conntrack_amanda from netfilter
that's the culprit. I haven't tested yet, but others have confirmed it.
I
It is really best to post to only ONE of the -users or -hackers
lists. Decide if it is about the code of amanda, then submit
to -hackers. For the overwhelming majority of posts, they
concern usage of amanda and should go to -users.
On Fri, Nov 05, 2004 at 08:05:48PM +, Gavin Henry wrote:
Would people please stop cross-posting between -users and -hackers.
If your message is about using amanda, send it to -users. If it's
about the source, send it to -hackers.
Don't mean to single out Gavin here. This has happened several times
recently, each then multiplied by all the followups.
On Fri, Nov 05, 2004 at 03:24:40PM -0500, Jon LaBadie wrote:
It is really best to post to only ONE of the -users or -hackers
lists. Decide if it is about the code of amanda, then submit
to -hackers. For the overwhelming majority of posts, they
concern usage of amanda and should go to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 05 Nov 2004 20:24, Jon LaBadie wrote:
It is really best to post to only ONE of the -users or -hackers
lists. Decide if it is about the code of amanda, then submit
to -hackers. For the overwhelming majority of posts, they
concern usage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 05 Nov 2004 20:42, you wrote:
Would people please stop cross-posting between -users and -hackers.
If your message is about using amanda, send it to -users. If it's
about the source, send it to -hackers.
Again, sorry. I thought it was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
Just a thought,
Would there be any benefit of implementing host lookups etc via LDAP for
enteprise class backups?
- --
Kind Regards,
Gavin Henry.
Managing Director.
T +44 (0) 1467 624141
M +44 (0) 7930 323266
F +44 (0) 1224 742001
E
Hi, Jon,
on Freitag, 05. November 2004 at 22:09 you wrote to amanda-users:
JL On Fri, Nov 05, 2004 at 03:24:40PM -0500, Jon LaBadie wrote:
It is really best to post to only ONE of the -users or -hackers
lists. Decide if it is about the code of amanda, then submit
to -hackers. For the
Hello Everyone,
I'm finally starting my backup on the server with the large file system. I'm
receiving errors and the DLE did not run as the excludes never took affect.
Here's excerpts from the amdump log:
/etc/amanda/normal/disklist, line 21: dump type parameter expected
I have one computer which is busy now, and is dumping *very* slowly.
I want to kill the dumper for this computer. Killing all the dumpers
is even OK. I could do a killall dumper, but it seems a bit crude.
Is there a more polite way of killing a dumper, or just telling it to
give up on a DLE?
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You think there is an order to the tapes, 2 follows 1 etc. Amanda could
care less what new tape it writes to next. If you put in tape3 next,
amanda's order will have 3 following 1 in the future. If you labelstr
allows it (tape.*) amanda will
On Fri, Nov 05, 2004 at 09:53:53PM -, James Marcinek enlightened us:
I'm finally starting my backup on the server with the large file system. I'm
receiving errors and the DLE did not run as the excludes never took affect.
Here's excerpts from the amdump log:
/etc/amanda/normal/disklist,
On Fri, 5 Nov 2004, Kevin Dalley wrote:
I have one computer which is busy now, and is dumping *very* slowly.
I want to kill the dumper for this computer. Killing all the dumpers
is even OK. I could do a killall dumper, but it seems a bit crude.
Is there a more polite way of killing a
As a member of the AMANDA Core Team I am pleased to announce another
update of the AMANDA-docs.
There have been many small fixes but the main improvement is the
integration of the Manual Pages into the main document of the
so-called AMANDA-HOWTO-Collection. This enables us to get even more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I suspect you have only done one backup, thus only previously used one
tape.
You think there is an order to the tapes, 2 follows 1 etc. Amanda could
care less what new tape it writes to next. If you put in tape3 next,
amanda's order will have
When I run with:
autoflush on
the size of the flushed data is not taken from the total size of the
tape.
Is there a way, when using autoflush, to have the amdump use the tape
size minus the size of the previous data?
--
Kevin Dalley
[EMAIL PROTECTED]
25 matches
Mail list logo
