Coda File System

Re: Amanda differences: 2.4.4p1 (installed) vs. 2.4.4-2 (compiled)

From: Jason A. Pattie <>
Date: Wed, 25 Feb 2004 12:36:24 -0600
Hash: SHA1

Jason A. Pattie wrote:
| Jason A. Pattie wrote:
| | Jason A. Pattie wrote:
| | | I get "ERROR [Volume check for coda.root failed]" after running
| amcheck.
| |
| | And now I may know why.  In /usr/lib/amanda/calcsize.coda, I changed
| | LOGFILE to /tmp/calcsize.coda-`date +%Y%m%d%H%M%S` and ran it as root.
| | Seemed to work perfectly.  su - backup.  Ran it as the backup user
| | (which is what Debian uses for Amanda).  The following error spit out:
| |
| | Wed Feb 25 12:08:38 CST 2004 -- sendsize coda.root started
| | /usr/lib/amanda/calcsize.coda: line 1: volutil: command not found
| |
| | Apparently, backup cannot see the volutil command in its PATH.  I'm
| | going to hardcode the location, since backup does not by default have
| | its PATH set to /usr/sbin... etc., and try again.  I'm also wondering if
| | the backup user has the correct permissions to be allowed to export
| | data, etc. from coda volumes?
| Well, getting a little closer, maybe?  Running calcsize.coda as backup,
| I now get:
| Wed Feb 25 12:15:59 CST 2004 -- sendsize coda.root started
| V_BindToServer: binding to host <coda file server name>
| And that's it.  Hmm.

Unfortunately, I figured it out.  I found out that the backup user needs
to be able to obtain an authentication token in order to use volutil.
This was accomplished by changing group ownership and permissions on the
/vice/db/ file to be owned by the backup group and readable to
the backup group.  Once I did that, 'amcheck daily -c' worked like a charm.

Jan, are you perhaps running amanda as root and not as a backup (or
other) user?  Or had you already done something similar (or completely
different) to allow the backup user access to volutil information?


- --
Jason A. Pattie
Xperience, Inc. (
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Debian -


This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
Received on 2004-02-25 13:38:44