Hi Jan/ All,

The issue was with the realms which did not contain the server FQDN and ipaddress

[EMAIL PROTECTED]:/coda# more /usr/local/etc/coda/realms
node2.bluebarracuda.eu 192.168.1.70

I restarted the server and it was working.

...

I created a volume using the following

[EMAIL PROTECTED]:/coda# createvol_rep volume node2.bluebarracuda.eu
and the following was created in the coda directory

[EMAIL PROTECTED]:/coda# ls
node2.bluebarracuda.eu@

and ROOTVOLUME in /vice/db/ROOTVOLUME

[EMAIL PROTECTED]:/vice/db# more ROOTVOLUME
/coda

...

I tried to mount the volume created using the following but i got File Exist.

[EMAIL PROTECTED]:/coda# cfs mkmount node2.bluebarracuda.eu /web/
.: File exists
[EMAIL PROTECTED]:/coda#

--- Is this the proper way to do it??

Basically i want to have a volume created in /coda - ie /coda/volume1
And want all my client to RW access to this volume.

Please tell me how this can be done.

Many Thanks
Prashant












Jan Harkes wrote:
On Thu, Jun 07, 2007 at 01:00:56PM +0100, prashant wrote:
[EMAIL PROTECTED]:/vice/db# ps -ef
root 1290 1 0 Jun06 ? 00:00:00 auth2 root 1348 1 0 Jun06 ? 00:00:07 updatesrv root 1351 1 0 Jun06 ? 00:00:14 updateclnt -h node1.bluebarracuda.eu
root      1383     1  0 Jun06 ?        00:00:10 venus

*But i cannot create a volume.
[EMAIL PROTECTED]:/vice/db# createvol_rep test node1.bluebarracuda.eu
Failed to dump the current VRDB into /vice/db/VRList.new
...
[EMAIL PROTECTED]:/vice/db# volutil -h node1.bluebarracuda.eu dumpvrdb /vice/db/VRList V_BindToServer: binding to host node1.bluebarracuda.eu RPC2_NewBinding to server node1.bluebarracuda.eu failed with RPC2_NOBINDING (F)

Is the codasrv (Coda server) process running?
Are there errors in /vice/srv/SrvLog and/or /vice/srv/SrvErr?

Jan



--

*Prashant Ramhit*
/Technical/             

[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
d: +44 (0)20 7923 6870
t: +44 (0)20 7923 6840
www.bluebarracuda.com <http://www.bluebarracuda.com>      
*blue barracuda*
the lightwell
12-16 laystall street
london
ec1r 4pf        

Reply via email to