> > I mean, /net/useruv is 268842m ...
> Whoa, there. This implies you're trying to back up an NFS mounted
> area..
> That, in general, is a bad idea.
Well, actually, no. It is one of the nfs mounts, but this is the original
mount point, not the nfs mount itself. I mean, this is the system it is
mounted from. It is a local disk on this system. We just use the same
name so users don't get confused.
We are using tar 1.13.19, not ufsdump. Amanda is installed on the local
machine.
Although now I am getting a new error. We have 2 systems, arsd and arsd2,
that are configured the same way, but arsd has the following errors:
FAILURE AND STRANGE DUMP SUMMARY:
arsd /net/gnome lev 0 FAILED [Request to arsd timed out.]
arsd /net/user1 lev 0 FAILED [Request to arsd timed out.]
arsd /net/pdrs2 lev 0 FAILED [Request to arsd timed out.]
arsd /net/pdrs1 lev 0 FAILED [Request to arsd timed out.]
arsd /net/user30 lev 0 FAILED [Request to arsd timed out.]
arsd /net/data3 lev 0 FAILED [Request to arsd timed out.]
[many more...]
I'm not sure why this is the case. The amcheck says this:
Amanda Tape Server Host Check
-----------------------------
Holding disk /space/hold: 5221318 KB disk space available, that's plenty
NOTE: skipping tape-writable test
Tape arsd-01 label ok
Server check took 6.879 seconds
Amanda Backup Client Hosts Check
--------------------------------
ERROR: arsd NAK: amandad busy
Client check: 1 host checked in 0.056 seconds, 1 problem found
(brought to you by Amanda 2.4.2p2)
Any ideas?
lance
