I am in the process of migrating to 2.6.1, and the test client on OpeenBSD
is not working correctly at the moment. I am getting dumps that consist of
only the header, and no valid data.

I am aware of the problem, and it is on the list of things that will get
fixed. However, this is triggering a secondary problem. Every night the
directory created on the dumpdisk gets left behind. It contains these bad
files:

amstatus has the following to say:

pbuild3:wd0a                  0         0m flushed (22:29:17), PARTIAL
pbuild3:wd0a                  0         0m flushed (22:29:29), PARTIAL
pbuild3:wd0a                  0         0m finished (22:45:06), PARTIAL
pbuild3:wd0d                  0         0m flushed (22:29:20), PARTIAL
pbuild3:wd0d                  0         0m flushed (22:29:36), PARTIAL
pbuild3:wd0d                  0         0m finished (22:53:40), PARTIAL
pbuild3:wd0e                  0         0m flushed (22:29:24), PARTIAL
pbuild3:wd0e                  0         0m flushed (22:29:38), PARTIAL
pbuild3:wd0e                  0         0m finished (22:51:10), PARTIAL
pbuild3:wd0f                  0         0m flushed (22:29:26), PARTIAL
pbuild3:wd0f                  0         0m flushed (22:29:41), PARTIAL
pbuild3:wd0f                  0         0m finished (22:48:39), PARTIAL

Here are the files in a typical orphan directory:

-rw------- 1 amanda amanda 32788 2009-02-24 22:41 pbuild3.wd0a.0
-rw------- 1 amanda amanda 32788 2009-02-24 22:48 pbuild3.wd0d.0
-rw------- 1 amanda amanda 32788 2009-02-24 22:47 pbuild3.wd0e.0
-rw------- 1 amanda amanda 32788 2009-02-24 22:42 pbuild3.wd0f.0

Shouldn't the nightly backup be deleting these files, and the parent
directory? I am fairly certain that in the past, a failed backup did not
result in an orphan directory on the dumpdisk.


-- 
One of the main causes of the fall of the roman empire was that, lacking
zero, they had no way to indicate successful termination of their C
programs.