I'm currently having a problem with my nightly backups/dumps. All other
volumes work fine, but backup seems to be consistently having problems
with one particular volume:

01:30:15 Dumping 7f000009.2000013 to /backup1/30Jan2001/rachael.dorc.foolhq.com-7f000009.2000013 ...
01:38:23 WriteDump: Error RPC2_SEFAIL3 (F) in CheckSideEffect

01:38:23 Transmitted bytes 221184 != requested bytes 512000!

01:38:23 VolDump (3a06a1b4) failed on 2000014 with Unknown RPC2 return code 200

01:38:30 Dumping 7f000009.1000014 to /backup1/30Jan2001/deckard.dorc.foolhq.com-7f000009.1000014 ...
01:50:25 WriteDump: Error RPC2_SEFAIL3 (F) in CheckSideEffect

01:50:25 Transmitted bytes 221184 != requested bytes 512000!

01:50:26 VolDump (31d7d72) failed on 1000015 with Unknown RPC2 return code 200

01:50:31 Dump of volume 7f000009 failed!

The one unique characteristic of this volume that comes to mind
immediately is that I have several .iso images stored here (ie several
files > 600MB). The cloning process works fine, but it gets stuck on the
dump as seen above. All other volumes dump properly. Any ideas on why
this is occuring?

It also looks like VolDump is reporting the wrong volume id  in the
error messages. For 7f000009.2000013, it reports a failure on 2000014:
01:38:23 VolDump (3a06a1b4) failed on 2000014 with Unknown RPC2 return code 200

On a related note, is there any way to control whether backup dumps all
copies of replicated volumes? My servers are in sync most of the time,
so it seems a bit unnecessary to store two identical copies of a volume.
Perhaps backup could do a check to see if they are both the same, and if
so, just dump one of them? This would save a lot of storage space,
especially for large volumes that are pretty static. How do other people
handle this?

I'm currently running Coda 5.3.10 compiled with krb5 support on
Linux 2.2.16.

Thanks.

-- 
Stephan Koledin
Mad Scientist
The Motley Fool
http://fool.com