Hi gurus,

I have a weird one I can't figure out. The situation is a Solaris machine 
with a small RAID attached. The RAID is partitioned into four 80Gb 
filesystems. The amanda server is also Solaris so we're using ufsdump to 
back them up. Now three of the partitions back up fine, but the fourth 
gives the [no backup size line] error consistently. The partition isn't 
fuller than the other three, the same binaries, tape drive, buffer disk 
are being used for all four, so why would just one partiton give this 
error?  

Below is the output from an amdump run. The only strange things I can see 
(apart from the error) is that it thinks that 75253.71MB needs to go on 
1.12 tapes, when tapes are in fact 100Gb LTOs and the 'not enough space 
for slave process', whatever that means?

/-- snarl      /export/raid2 lev 0 FAILED [no backup size line]
sendbackup: start [snarl:/export/raid2 level 0]
sendbackup: info BACKUP=/usr/local/etc/amufsdump
sendbackup: info RECOVER_CMD=/usr/sbin/ufsrestore -f... -
sendbackup: info end
|   DUMP: Writing 32 Kilobyte records
|   DUMP: Date of this level 0 dump: Wed Apr 27 18:31:19 2005
|   DUMP: Date of last level 0 dump: the epoch
|   DUMP: Dumping /dev/rfssnap/1 to standard output.
|   DUMP: Mapping (Pass I) [regular files]
|   DUMP: Mapping (Pass II) [directories]
|   DUMP: Estimated 154119604 blocks (75253.71MB) on 1.12 tapes.
|   DUMP: Cannot create slave process: Not enough space
|   DUMP: The ENTIRE dump is aborted.
sendbackup: error [no backup size line]
\--------

If anyone has any ideas what I could be looking for, I'd be most grateful.

Chris