Amanda-Users

Just installed 2.5.1 - ufsdump error

2006-09-25 11:41:28
Subject: Just installed 2.5.1 - ufsdump error
From: "Christopher Davis" <giarmdok AT usa DOT net>
To: <amanda-users AT amanda DOT org>
Date: Mon, 25 Sep 2006 08:51:46 -0600
I just installed 2.5.1 as a new - clean install.


Amanda backups up the linux server that is the backup server with no
problems.

I added in a solaris 8 box but get the following errors now for every Solaris
DLE


server    /home1      lev 0  FAILED [/usr/sbin/ufsdump returned 3]



FAILED AND STRANGE DUMP DETAILS:

/--  server /home1 lev 0 FAILED [/usr/sbin/ufsdump returned 3]
sendbackup: start [server:/home1 level 0]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/usr/sbin/ufsrestore -f - ...
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
|   DUMP: Density must be a positive integer
|   DUMP: The ENTIRE dump is aborted.
sendbackup: error [/usr/sbin/ufsdump returned 3]
\--------


I look in the files on the client I see this in the sendbackup log:


sendbackup: debug 1 pid 6647 ruid 65000 euid 65000: rename at Sat Sep 23
03:50:05 2006
  sendbackup req: <DUMP /home1  0 1970:1:1:0:0:0 OPTIONS
|;auth=BSD;compress-fast;index;>
  parsed request as: program `DUMP'
                     disk `/home1'
                     device `/home1'
                     level 0
                     since 1970:1:1:0:0:0
                     options `|;auth=BSD;compress-fast;index;'
sendbackup: start: server:/home1 lev 0
sendbackup: time 0.048: spawning /usr/bin/gzip in pipeline
sendbackup: argument list: /usr/bin/gzip --fast
sendbackup-dump: time 0.049: pid 6649: /usr/bin/gzip --fast
sendbackup: time 0.052: dumping device '/dev/rdsk/c1t1d0s7' with 'ufs'
sendbackup: time 0.053: spawning /usr/sbin/ufsdump in pipeline
sendbackup: argument list: /usr/sbin/ufsdump dump 0usf 1048576 -
/dev/rdsk/c1t1d0s7
sendbackup: time 0.055: started backup
sendbackup: time 0.056: started index creator: "/usr/sbin/ufsrestore -tvf -
2>&1 | sed -e '
s/^leaf[        ]*[0-9]*[       ]*\.//
t
/^dir[  ]/ {
s/^dir[         ]*[0-9]*[       ]*\.//
s%$%/%
t
}
d
'"
sendbackup: time 0.066:  87:  normal(|):   DUMP: Density must be a positive
integer
sendbackup: time 0.069:  87:  normal(|):   DUMP: The ENTIRE dump is aborted.
sendbackup: time 0.164: index created successfully
sendbackup: time 0.167: error [/usr/sbin/ufsdump returned 3]
sendbackup: time 0.167: pid 6647 finish time Sat Sep 23 03:50:05 2006





The line that jumps out at me is this:
 /usr/sbin/ufsdump dump 0usf 1048576 - /dev/rdsk/c1t1d0s7


This ins't a valid command -  the word 'dump' is being interpreted as options
to ufsdump and as far as I can tell shouldn't be there - so where did that
come from and where can I get rid of it?


Chris




<Prev in Thread] Current Thread [Next in Thread>