Matthew Boeckman wrote:

Running amanda 2.4.2, and have configured for tapeless operation to spool backups to the holding disk. The holding disk is actually an NFS mounted volume on a SNAP server. Problem I'm having is how to define that 'partition'

the mount is 192.168.0.15:/amt_dump

Normally I would say something like:
holdingdisk  amt_dump {
    comment "blah"
    directory "/bkup/amanda"
    use 25 Gb
    chunksize 15Gb

Which seems fine to me. What's happening is that lvl 0's on my biggest partition are failing: amt /dev/sda9 lev 0 FAILED [dump larger than tape, but cannot incremental dump new disk]

Here's the disk usage for that partition:
/dev/sda9             122G  4.7G  111G   5%

There are 188G free on that holding disk! Why is amanda whining about this?

Will this magically go away if I upgrade to 2.4.3 and use the file: driver?

Matthew

--
Martin Hepworth
Senior Systems Administrator
Solid State Logic Ltd
+44 (0)1865 842300




**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************