Hi,

1) To shutdown venus cleanly, do the following as root

   # vutil -shutdown

2) To bring up venus again, first you have to umount /coda

   # umount /coda

   If there are some process hanging on coda space, you will get
   error message of "umount: Coda: device is busy".  In this case, you
   need to force all processes to leave coda space and umount
   again.   

   You can manually check which processes are still hanging on coda
   space (cd'ed into a coda directory, executing a file in coda space,
   opened a file in coda space etc).  In linux, you may
   find the utility program "fuser" useful.  For example, on my machine

   # fuser -m /coda
   /coda:               27979c

   showed that process 27979 was hanging on the coda space, the
   process happened to be a shell, so I instructed the shell to cd to
   a non-coda directory to leave coda space.

3) If you are sure all your processes have left coda space, but you
   still get the "device is busy" message when you umount, 
   you need to reboot your client machine to reset the state.
   (This should not happen often and is considered a bug.)   

4) After you have successfully umount /coda, you can bring venus up.

5) When starting venus, normally, you don't use the -init flag.  The
   -init flag must be used with care, the flag is intended to brain-wipe
   every data in the recoverable store.  If you updated some files in
   coda space *disconnected*, your data were not written to the server
   yet, so what was in your recoverable store were the last copy of your
   update.

Hope this help.

-- Yui Wah LEE (Clement)