-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
I've got coda 6 up and running without a problem on a freebsd 5.4
distribution.  However, I haven't been quite able to grasp how the
coda partitions relate to actual available space.  I've read through
the documentation on the website, but I think I'm just missing something.

On my test system (before I installed coda), I have a seperate raid 5
array that measures approx. 484 gigs after formatting, etc. mounted as
/data.  After running the vice-setup script, starting coda, doing
createvol_rep, configuring venus, and starting venus, issuing df -H, I
come up w/this...

/dev/da0s1d           484G     68G    377G    15%    /data
CODA                   74G      0B     74G     0%    /coda

The first line is the original directory.  However, why is it that
coda allocates 74 gigs and what controls this?  I've altered the size
of the number of files in the vice-setup script to see if it makes a
difference, but to no avail.

I'd greatly appreciate an explanation on how coda comes to this
conclusion before I slice up the /dev/da0 disk into partitions.
Obviously, I'm either missing something from the documentation or it
just hasn't been documented.

TIA

- --
MicroStrain, Inc.
Phone: 802.862.6629
Fax: 802.863.4093
Web: www.microstrain.com

To obtain a copy of my PGP key, please, visit pgp.mit.edu
through your web browser or through your GnuPG/PGP program
and search for my email address.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFDLt2DHgZlOCJZmW8RAgaRAJ9V4eCX2ZhihldLNtosqIGB9gxgygCcDcdY
sYOuPG3PLn3IB6e/2d7tjcg=
=/1JU
-----END PGP SIGNATURE-----